At Wed, 12 Jan 2011 13:57:06 -0700, Jon Rafkind wrote: > On 01/03/2011 02:11 PM, Matthew Flatt wrote: > > At Mon, 3 Jan 2011 14:55:05 -0500, Sam Tobin-Hochstadt wrote: > >> On Mon, Jan 3, 2011 at 2:51 PM, Robby Findler > >> <ro...@eecs.northwestern.edu> wrote: > >>> Or maybe there is another possible solution that involves changing how > >>> the distribution and or the docs build works? > >> I think the conventional solution is for `make install' to do much > >> less work than it current does. In "normal" Make-built software, > >> `make' does all of the compilation, and `make install' just does the > >> copying. That way, `make install' wouldn't be doing things like > >> reading preferences and creating the '.racket' directory. > > Well, moving work from `make install' to `make' does nothing in itself. > > What you're suggesting is that we change what `make install' produces. > > > > In particular, I think you're suggesting that no user-specific actions > > take place as a result of a build and install. That change sounds ok to > > me, and it can be accomplished by passing `--no-user' to `raco setup' > > during `make install'. > > > > Unless anyone objects, I'll push that change soon. > > > > Was this change pushed? I did a simple search but didn't find it.
Not until now. I kept looking for our old rationale, but I couldn't find it and I've given up. The no-user-setup-on-install default is controlled by `configure', and there's a new `--enable-usersetup' flag to get the old behavior. _________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
