Hello again, <br><br>I was able to resolve my problem. First I renamed the frtime collection in the install path. This resulted in racket complaining that the collection couldn't be found. Next, I linked to the collection within the frtime source directory. <br>
<br>raco link path/to/github/repo/directory<br><br>Following linking to this location, the language declaration resolved to the frtime language within my github tree. <br><br>Thanks all, <br>-Patrick<br><br><div class="gmail_quote">
On 24 July 2012 18:52, Patrick Mahoney <span dir="ltr"><<a href="mailto:paddy.mahoney@gmail.com" target="_blank">paddy.mahoney@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5">Hello All,<br><div class="gmail_quote"><br>I forked the github Racket repo, and created a new branch in order to update Frtime from the scheme or mzscheme #langs to Racket. This has been progressing well, until I ran into a small issue that I think likely affects most individuals working on Racket source for which collections exist in the collection paths. <br>
<br><pre><div><span>(</span><span>module</span> <span>animation</span> <span>frtime<br>...<br></span></div></pre><br>-Despite making changes to the frtime language, excising the scheme and mzscheme languages within the source that was checked out, it became apparent that this declaration and others referring to collections were relying on the imports defined from the mzscheme lang. After running Check Syntax, right-clicking on the lang declaration, and opening the files all the way down to a file where changes had been made (say lang-utils.rkt), the unedited source was visible. This source showing (sans my edits) was that found within the C:/Program Files/Racket/collects/frtime directory, rather than my github racket source directory. <br>
<br>How does one go about unregistering a collection such that all references to that collection subsequently look not into the collections directory, but compile and run the files from within your checked out source? I guess this question could likely could be generalized to, "How do Racket developers make edits to source files backing collections and run them without references to collections referring to the pre-compiled collections, or those in the Racket installation?". I am interested in how to resolve this problem, and I apologize that I don't yet know the language well enough to formulate the problem in the correct terms. <br>
<br>Can anyone provide some guidance here? <br><br>For anyone interested in the branch itself, find it at: <a href="https://github.com/paddymahoney/racket/commits/frtime-update" target="_blank">https://github.com/paddymahoney/racket/commits/frtime-update</a><br>
<br>Thank you all!<span><font color="#888888"><br>-Patrick<br><br>
</font></span></div><br>
</div></div></blockquote></div><br>