[gentoo-dev] portage again :)

[gentoo-dev] portage again :)

[Mathijs Kwik (-=TRoXX=-)]

daniel,

I'm playing with the $ROOT-variable to create some script that builds a
build-environment...
ofcourse everything has to be built statically in the first phase, so I need
USE-flags "build static" I guess...
I encounter some strange behaviour of portage every now and then, can you
explain me if $ROOT is water-proof at the moment? I mean does portage use
$ROOT/var/db and $ROOT/env/make.conf and stuff? I noticed it sometimes
does... but sometimes I really doubt.
for example... when I make portage install portage it first builds zlib, and
then glibc... which is strange, since zlib also depends on glibc...
I didn't test it in a non $ROOT environment, but I suspect that portage
doesn't check dependancies in $ROOT/var/db or multi-level dependancies have
some small bugs (dependancies of dependancies).
any hints?

/Mathijs

Re: [gentoo-dev] portage again :)

[Daniel Robbins]

On Thu, Jun 21, 2001 at 04:07:16PM +0200, Mathijs Kwik (-=TRoXX=-) wrote:

> I'm playing with the $ROOT-variable to create some script that builds a
> build-environment...  ofcourse everything has to be built statically in the
> first phase, so I need USE-flags "build static" I guess...  I encounter some
> strange behaviour of portage every now and then, can you explain me if $ROOT
> is water-proof at the moment? I mean does portage use $ROOT/var/db and
> $ROOT/env/make.conf and stuff? I noticed it sometimes does... but sometimes I
> really doubt.  for example... when I make portage install portage it first
> builds zlib, and then glibc... which is strange, since zlib also depends on
> glibc...  I didn't test it in a non $ROOT environment, but I suspect that
> portage doesn't check dependancies in $ROOT/var/db or multi-level
> dependancies have some small bugs (dependancies of dependancies).  any hints?

The first thing I'd do is check with achim to see how he builds the build
environments, and use his procedure.  ${ROOT}/var/db is supported; ${ROOT}/etc
is only partially supported.  The only thing it reads from ${ROOT}/etc is
${ROOT}/etc/make.profile/virtuals to do virtual package resolution.  Everything
else comes from /etc, not ${ROOT}/etc.

I had a version of Portage that would use ${ROOT}/etc for all its settings, but
achim and I decided that it was unnecessary (I can't remember the reason; you
may want to check with him to see if he remembers why we didn't go with a fully
relocatable /etc.)  I think it may be that USE variables really can't be changed
mid-stream, since other packages may have been previously built with these deps,
but I'm probably wrong.

Best Regards,

-- 
Daniel Robbins					<drobbins@gentoo.org>
President/CEO					http://www.gentoo.org 
Gentoo Technologies, Inc.