From: Stroller <root@stellar.eclipse.co.uk>
To: <vapier@gentoo.org>, <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] Re: [gentoo-core] boostrap.sh problem?
Date: Sun, 13 Jul 2003 03:03:06 +0100 [thread overview]
Message-ID: <BB367C6A.17F2C%root@stellar.eclipse.co.uk> (raw)
In-Reply-To: <200307121854.03357.vapier@gentoo.org>
On 12/7/03 11:53 pm, "Mike Frysinger" <vapier@gentoo.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Saturday 12 July 2003 15:22, Daniel Robbins wrote:
>> On Sat, Jul 12, 2003 at 12:37:52PM -0400, Grant Goodyear wrote:
>>> I asked hunt3r to try bootstrapping again w/o "static" in USE, and so
>>> far it seems to be working for him. Should bootstrap be filtering that
>>> use flag?
>>
>> Bootstrap doesn't filter out any use flags. They need to be set correctly.
>
> you cant sit there and say that and then not tell people what will break a
> bootstrap ... either the bootstrap process should filter static from USE or
> the install docs should be updated with a note that says 'USE=static' will
> break bootstrap, please do not use this until you are past stage3
Erm... I'm not sure if this is a dumb-question... but I thought that
bootstrap should use only the USE settings in
/usr/portage/profiles/build/make.defaults ?
$grep USE make.defaults
USE="build"
I note that sys-apps/sed is listed in /usr/portage/profiles/build/packages
Is it possible that hunt3r has found some clever undocumented way to
manipulate his USE flags too early in his installation..?
Stroller.
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-07-13 2:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-12 15:54 [gentoo-dev] boostrap.sh problem? Grant Goodyear
2003-07-12 16:37 ` [gentoo-dev] Re: [gentoo-core] " Grant Goodyear
2003-07-12 19:22 ` Daniel Robbins
2003-07-12 22:53 ` Mike Frysinger
2003-07-13 2:03 ` Stroller [this message]
2003-07-16 2:15 ` Mike Frysinger
2003-07-13 5:18 ` Mike Frysinger
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=BB367C6A.17F2C%root@stellar.eclipse.co.uk \
--to=root@stellar.eclipse.co.uk \
--cc=gentoo-dev@gentoo.org \
--cc=vapier@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