[plt-dev] Re: Generated files and co-existing copies of DrScheme
On Nov 20, Carl Eastlund wrote:
> On Fri, Nov 20, 2009 at 5:14 PM, Eli Barzilay <eli at barzilay.org> wrote:
> >>
> >> The act of unpacking the nightly build will not do so, but the
> >> inevitable subsequent act of installing planet packages
> >> will. Thus I'm not sure what the nightly build will save me, in
> >> terms of allowing separate copies of PLT Scheme to coexist.
> >
> > Yes, you have to do the planet part yourself either way. (But I
> > don't see how controlling the addons directory will help there.)
>
> The same way it will help anywhere else.
My question is how -- what's this "same way"?
> By directing one nightly build to install stuff in a different place
> than the other. Am I missing something obvious here about your
> point? Because you seem to be contradicting my original premise,
> without coming out and saying so.
I'm not making any point -- I might be missing something about either
the problem or the suggested solution, and I just didn't ask about it
so far. If you're still planning to run a build every day, then what
is exactly the problem? My best guess is that you're trying to avoid
the wait while a build is happening -- it's only a guess, but if this
is the case then how about using the ultimate parameter:
mkdir ~/plt-build
HOME=~/plt-build ...build everything...
move directories from ~/plt-build to where they usually live
> Re: command line versus environment, a quick test showed me that,
> for instance, mzscheme accepts -X but plt-help does not. So a "run
> PLT executables via script based on $PLTHOME" solution suddenly has
> to special case different options for each command. The nice thing
> about environment variables is that the same set works for every
> command; extra ones are ignored.
You're right, that's a general problem that already exists with `-X'
and the rest.
--
((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay:
http://barzilay.org/ Maze is Life!