public inbox for gentoo-releng@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-releng@lists.gentoo.org
Subject: [gentoo-releng] USE flags and stages 1 and 2
Date: Mon, 31 Oct 2005 16:09:30 -0500	[thread overview]
Message-ID: <1130792970.26789.120.camel@cgianelloni.nuvox.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1665 bytes --]

I'm starting to get more and more bugs from users whom have decided,
against the recommendation of those of us in Release Engineering, to do
a stage1 or stage2 installation using their custom USE flags, and
finding that their installation is unable to complete properly.  The
problem stems from more and more packages adding more and more USE
flags.  We already recommend that all users perform a stage3
installation, but this doesn't appear to be enough to resolve the
problem.  What it really boils down to is the inability for us to test
with all of the possible USE flag combinations and ever get a release
out the door.

As it stands, I only see a few options, none of which sound very good:

1.  Only release stage3 tarballs
2.  Inform users that only stage3 will be supported
3.  Change the documentation to recommend users not change USE flags
until after the completion of "emerge -e system"

In pretty much every case, the real answer is "quit using stage1 if you
don't know what you're doing" but unfortunately, we're going to get the
pointless "but Gentoo is about choice" "argument" that really has no
bearing on the truth of what is Gentoo.  Gentoo is *not* about choice.
Gentoo is about empowering the user to make the system as he sees fit.
This means there is a certain expectation that when you start fiddling
with stuff, you're going to pick up the pieces on your own.  At any
rate, the problem is only going to get worse as more and more USE flags
are added.

What can we do to curb this problem?

-- 
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2005-10-31 21:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-31 21:09 Chris Gianelloni [this message]
2005-10-31 21:43 ` [gentoo-releng] USE flags and stages 1 and 2 M. Edward (Ed) Borasky
2005-10-31 21:59   ` Michael Crute
2005-10-31 22:26     ` Chris Gianelloni
2005-10-31 22:27       ` [gentoo-releng] " Anthony Gorecki
2005-10-31 22:45         ` Chris Gianelloni
2005-10-31 22:09   ` [gentoo-releng] " Chris Gianelloni
2005-10-31 21:51 ` Michael Crute
2005-10-31 22:18   ` Chris Gianelloni
2005-10-31 22:32     ` Michael Crute
2005-10-31 22:51       ` Chris Gianelloni
2005-10-31 21:53 ` Jory A. Pratt
2005-10-31 22:21   ` Chris Gianelloni
2005-10-31 22:22 ` [gentoo-releng] " Anthony Gorecki
2005-10-31 22:44   ` Chris Gianelloni
2005-11-01 19:18     ` Sven Vermeulen
2005-11-01 20:01       ` Chris Gianelloni
2005-11-02 14:30         ` Gustavo Zacarias
2005-10-31 22:25 ` [gentoo-releng] " Seemant Kulleen
2005-10-31 22:36   ` Chris Gianelloni

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=1130792970.26789.120.camel@cgianelloni.nuvox.net \
    --to=wolf31o2@gentoo.org \
    --cc=gentoo-releng@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