seperate static build profile

Jason Gurtz jason at
Wed Jan 23 10:55:05 PST 2002

> <setenv>
>     <variable>foo</variable>
>     <value>bar</value>
> </setenv>
> :)
> But there is a problem with this.
> <setenv> would have to be called (once) before every action inside
> <chroot>, because environment is lost when you stop executing.
> I was thinking if we should somehow improve <chroot> - for
> now it's not very
> smart, it can only change root directory and that's it.

Yea, it seems like you'd have to either look for <setenv> pairs right
after <chroot> and then keep that in a table in memory until a </chroot>
had occured.  I'm trying to see what side effects that would have...




Unsubscribe: send email to listar at
and put 'unsubscribe alfs-discuss' in the subject header of the message

More information about the alfs-discuss mailing list