Re: [racket-dev] raco pkg install should default to linking for filesystem packages
So `--link' could be the default, while `--copy' (?) could disable special handling of directory sources? That sounds fine. I mean, I am unlikely to ever use --copy, but whatever makes sense to expose in terms of the underlying model. It could be useful if the directory is on a remote computer, but this will probably be a less frequent case. Laurent _ Racket Developers list: http://lists.racket-lang.org/dev
[racket-dev] raco pkg install should default to linking for filesystem packages
Hi all, When I have a directory foo/, containing a single-collect package, and I install it with raco pkg install foo/, it seems to copy the contents of the directory, meaning local edits are not found by the system. Instead I have to raco pkg install --link foo/. I would prefer it if --link were the default. Cheers, Tony _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] raco pkg install should default to linking for filesystem packages
I like this change; thanks for suggesting it! Robby On Wed, Jul 31, 2013 at 1:38 PM, Tony Garnock-Jones to...@ccs.neu.eduwrote: On 07/31/2013 02:24 PM, Matthew Flatt wrote: I think it often makes sense for command-line tools to have weird rules[*], I agree with you. UIs have to be humane and ergonomic for our weak, squishy meat-bodies to cope. (Though of course the underlying model has to be sensible too ;-) ) especially if there's a flag to enable more consistent rules. Right, to expose a machine interface to the raw underlying model. Porcelain and plumbing. So `--link' could be the default, while `--copy' (?) could disable special handling of directory sources? That sounds fine. I mean, I am unlikely to ever use --copy, but whatever makes sense to expose in terms of the underlying model. Cheers, Tony _ Racket Developers list: http://lists.racket-lang.org/**dev http://lists.racket-lang.org/dev _ Racket Developers list: http://lists.racket-lang.org/dev
