On Sun, 03 Sep 2006 00:11:21 +0200, André Detsch <[EMAIL PROTECTED]> wrote:
On 9/2/06, Jonas Karlsson <[EMAIL PROTECTED]> wrote:
Isn't LinkOrExpandAll needed in building the environment? Then why is it
symlinked in update_tools() in SetupChrootEnv?
I'm not sure if I got the question, but the reason why LinkOrExpandAll
is linked to the ChrootCompile './' directory is to make it easy to
run this tool in systems other than GoboLinux.
Problem is that since ported to C one has to do "make" on the scripts, to
get the LinkOrExpandAll executable. Before that the created link is dead.
That's why I added the "make" call.
Actually, I've talked
with Hisham, and we agreed that it would be good to make ChrootCompile
more '/Programs' friendly (like BuildLiveCD, for example).
I haven't experimented much with these tools so I'm not really sure what
you mean here.
Please feel free to do any question about how to run ChrootCompile, so
we got, at least, some ad-hoc documentation of the most non-obvious
points :)
Ok, I'll ask questions as I get some.
First question: why does ChrootCompile install the exact same packages as
SetupChrootEnv? Wouldn't it be smarter to just do a check first?
--
/Jonas
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
_______________________________________________
gobolinux-devel mailing list
[email protected]
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
