From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] internal use only use flags
Date: Mon, 09 Jul 2007 12:16:06 -0700 [thread overview]
Message-ID: <1184008566.8412.25.camel@inertia.twi-31o2.org> (raw)
In-Reply-To: <468E866B.8080905@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]
On Fri, 2007-07-06 at 20:14 +0200, Marijn Schouten (hkBst) wrote:
> bootstrap - !!internal use only!! DO NOT SET THIS FLAG YOURSELF!, used during
> original system bootstrapping [make stage2]
> build - !!internal use only!! DO NOT SET THIS FLAG YOURSELF!, used for
> creating build images and the first half of bootstrapping [make stage1]
> It's probably a big pain to do this.
Changing build and bootstrap would require changes to a few packages in
system, but also to catalyst. It would completely break all versions of
catalyst prior to the "fixed" version for stage building.
Basically, we'd have to support both for at least a little while until
we got all of the older versions of catalyst out of use/support. I'd
need to stabilize catalyst 2.x and remove 1.x, at minimum.
It could be done, I just don't think the amount of work required for
what it otherwise a cosmetic change to be worth it.
--
Chris Gianelloni
Release Engineering Strategic Lead
Alpha/AMD64/x86 Architecture Teams
Games Developer/Council Member/Foundation Trustee
Gentoo Foundation
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-07-09 19:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-06 18:14 [gentoo-dev] internal use only use flags Marijn Schouten (hkBst)
2007-07-06 18:16 ` Petteri Räty
2007-07-06 18:41 ` Mike Frysinger
2007-07-09 19:16 ` Chris Gianelloni [this message]
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=1184008566.8412.25.camel@inertia.twi-31o2.org \
--to=wolf31o2@gentoo.org \
--cc=gentoo-dev@lists.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