From: "Mathijs Kwik (-=TRoXX=-)" <troxx@segfault.nl>
To: <gentoo-dev@cvs.gentoo.org>
Subject: [gentoo-dev] portage again :)
Date: Thu Jun 21 08:01:03 2001 [thread overview]
Message-ID: <007b01c0fa5b$9969ce70$840aa8c0@icgroup.nl> (raw)
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
next reply other threads:[~2001-06-21 14:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-21 8:01 Mathijs Kwik (-=TRoXX=-) [this message]
2001-06-21 13:33 ` [gentoo-dev] portage again :) Daniel Robbins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='007b01c0fa5b$9969ce70$840aa8c0@icgroup.nl' \
--to=troxx@segfault.nl \
--cc=gentoo-dev@cvs.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox