On Sun, Dec 2, 2012 at 10:38 AM, Matthew Flatt <mfl...@cs.utah.edu> wrote: > Who here has tried using `raco link' for development?
I use `raco link` for all of my development -- once `raco link` was released, I basically gave up on Planet1 and used `raco link` for everything. > The default mode is user-specific but not version-specific, and I've > found that default to be inconvenient. Usually, it turns out, I want an > installation-specific link, because I want it linked only for my > development version of Racket. When I get to the point that I do want > to use a different Racket version, it's a pain to juggle the links or > make a copy for different version. I look forward to using packages, > installation-specific links, and version-specific installs that are > taken as snapshots of the git repo. I have mostly the opposite impression of `raco link`. I like the default behavior, but that may be a result of my use of a set of scripts [1] for managing Racket installations that makes basically everything into installation-specific packages. One additional issue with version-specific installs that I just thought of -- imagine a student installing a course package on a lab computer, and then Racket being upgraded during the semester. [1] https://github.com/takikawa/racket-dev-goodies -- sam th sa...@ccs.neu.edu _________________________ Racket Developers list: http://lists.racket-lang.org/dev
