At Tue, 17 Feb 2015 14:12:54 -0500, Sam Tobin-Hochstadt wrote:
> Regardless of that, though, I think we should switch to updating only
> "main-distribution" (and perhaps "main-distribution-tests"). I doubt
> people expect `make` in the Racket source tree to update their
> software somewhere else on their machine -- I certainly would be very
> unpleasantly surprised if that happened to me when rebuilding some
> other language I had installed.

I have trouble seeing the comparison to other software. I don't know of
anything else with an in-place build option, where you can install or
link additional packages in place, and you can also pull core updates,
and somehow it all works. The examples I have seen are all more like
`make unix-style`, where there's a clear separation of the source and
the installed form. In that case, the issues we're looking at here
don't come up.

Does another system have a Racket-like in-place option (that works
better)?


At Tue, 17 Feb 2015 17:40:36 -0500, Matthias Felleisen wrote:
> Speaking as the user I am, I really like it that make updates 
> my extra-pkgs. 

Package scope provides one a way to get these different behaviors. The
current `make` updates only packages that are in installation scope,
and it also sets installation scope to be the default, so that's why
`make` tends to update everything that is installed. Maybe Sam should
install additional packages in user scope, and then `make` won't try to
update them.

Another possibility is that the packages installed by `make` should go
into a scope that's even deeper than installation scope. That's how the
pre-split organization worked, and I sometimes think that we should go
back to that. But it's more complex, and it would work less well for
Matthias and others who benefit from the current `make` behavior.

Overall, my sense is that the current defaults work right for people
with the least expertise, but we can refine our tools to provide
options to people with more expertise.

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/racket-dev/20150217234131.86F396501B8%40mail-svr1.cs.utah.edu.
For more options, visit https://groups.google.com/d/optout.

Reply via email to