dsaferite at yahoo.co.uk
Thu Mar 21 01:28:09 PST 2002
I like the idea of <chroot>, <su>, and <setenv> but for simplicity (or mybe to make it more complicated) why couldn't we have a:
<stage name="Ch.5 - Installing Bash" root="/some/dir" user="lfsuser" group="lfs" env="E=mc2">
You could use the attibute addenv to append to the env. and you would have all env changes be aplicable only to elements of the stage tag. I mean, if you look at it, every time you do a setenv or su or chroot you are entering a 'stage' of the building process, no? Comments/Flames welcome. =)
On Wed, 20 Mar 2002 11:55:52 +0100
Neven Has <haski at sezampro.yu> wrote:
> On Wed, Mar 20, 2002 at 11:44:38AM +0100, Neven Has wrote:
> > On Wed, Mar 20, 2002 at 10:24:36AM +0000, Mark Ellis wrote:
> > > No, you're right, it could get a bit limiting. Ok, how about a general
> > > parent element, can't think of a name at the moment, that encapsulates
> > > environment variable setting, effective user and group, and anything
> > > else we think we need later. Might be a bit tidier. This element would
> > > of course only change the environment for the items that were specified.
> > I thought about it, and that's where <stage> might be used too?
> > But on the other hand, there's something good about having a separate,
> > clean <chroot> and <su> elements...
> Um, <setenv>, not <chroot>. :)
> Unsubscribe: send email to listar at linuxfromscratch.org
> and put 'unsubscribe alfs-discuss' in the subject header of the message
Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe alfs-discuss' in the subject header of the message
More information about the alfs-discuss