From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-core@lists.gentoo.org
Cc: gentoo-releng@lists.gentoo.org, gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: [gentoo-core] x86 2004.2 Profile
Date: Fri, 09 Jul 2004 10:42:59 -0400 [thread overview]
Message-ID: <1089384178.11036.43.camel@localhost> (raw)
In-Reply-To: <1089380082.32612.3.camel@woot.uberdavis.com>
[-- Attachment #1: Type: text/plain, Size: 1483 bytes --]
On Fri, 2004-07-09 at 09:34, John Davis wrote:
> Is this that necessary? Why couldn't we merge this stuff into the
> default 2004.0 profile? It would impact more users that way (and even
> more if it was integrated into the 1.4 profile). With stackable profiles
> on their way (the only blocker now is the bootstrap script which is
> being worked on), does it make sense to create yet another profile?
For consitency's sake, yes, it is necessary. I don't want to build a
machine today using the 2004.0 profile and build a machine tomorrow
using *the same profile* and have one using xfree and one using
xorg-x11.
It also diminishes the number of bugs that will crop up from confused
users. Personally, I believe that a profile should never be changed
once it is created, as it introduces many of those "undocumented
changes" that our users are starting to get tired of seeing. We have an
obligation to our users. A 24K profile being added to the portage tree
will not kill us. Hopefully, we'll be getting rid of all of the
"legacy" profiles in the future, and this profile will be deleted, but
for now, I think it is absolutely necessary.
I also think that this needs to be discussed on -dev and not -core,
which is why I sent my emails there, as this directly impacts our users
and is something I am sure they're interested in.
--
Chris Gianelloni
Release Engineering QA Manager/Games Developer
Gentoo Linux
Is your power animal a penguin?
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next parent reply other threads:[~2004-07-09 13:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1089375713.8755.5.camel@antares.hausnetz>
[not found] ` <1089380082.32612.3.camel@woot.uberdavis.com>
2004-07-09 14:42 ` Chris Gianelloni [this message]
2004-07-09 15:37 ` [gentoo-dev] Re: [gentoo-core] x86 2004.2 Profile Grant Goodyear
2004-07-09 16:11 ` [gentoo-dev] " Chris Gianelloni
2004-07-09 17:15 ` John Davis
2004-07-09 18:12 ` Dylan Carlson
2004-07-09 18:28 ` Chris Gianelloni
2004-07-09 20:00 ` Andrew Gaffney
2004-07-09 20:37 ` Sami Samhuri
2004-07-09 21:07 ` Donnie Berkholz
2004-07-09 23:16 ` Spider
2004-07-10 18:23 ` Chris Gianelloni
2004-07-10 19:23 ` Spider
2004-07-10 19:48 ` George Shapovalov
2004-07-10 21:36 ` Dylan Carlson
2004-07-12 1:30 ` John Davis
2004-08-04 10:52 ` Paul de Vrieze
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=1089384178.11036.43.camel@localhost \
--to=wolf31o2@gentoo.org \
--cc=gentoo-core@lists.gentoo.org \
--cc=gentoo-dev@lists.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