<setenv>, <stage>

Mark Ellis mark.uzumati at virgin.net
Mon Apr 1 14:19:43 PST 2002


On 2002.04.01 23:13 Jesse Tie-Ten-Quee wrote:
> Yo,
> 
> On Mon, Apr 01, 2002 at 11:06:37PM +0100, Mark Ellis wrote:
> > I see what you mean, but i still like the idea. Maybe it would
> improve
> > readability to have the stage name as an attribute, it would then be
> 
> > more obviously attached to that particular stage ? Still keep all
> the
> > other stuff in <stageinfo>. Or maybe it just shouldn't be a
> replacement
> > for the *build stuff, but instead used specifically for modifying
> the
> > environment, and i use environment in its broad term, including user
> 
> > and group as well as variables ?
> 
> What if we used.. Like Lee, you and myself have tried to suggest the
> name as an attributed, So that we have like;
> 
> <stage name="build">
>     <make>
> 	<dir>/usr/src/sed-3.02</dir>
>     </make>
> </stage>
> 
> And for things like, su/user/group/env, just add in elements, like;
> 
> <stage name="setup">
>     <env>
> 	<name>CPPFLAGS</name>
> 	<value>blahal</value>
>     </env>
> 
>     <configure>
> 	<dir>/usr/src/blah-0.1</dir>
> 	<option>--prefix=/usr</option>
>     </configure>
> </stage>
> 
> And it gets unset when it exit's out of this stage?  I duno, just an
> idea that popped into my head.
> 

I think there may still be a place for <stageinfo> when setting the 
environment etc. just to group all the settings together, just IMHO.

Mark
-- 
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 mailing list