From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-releng@lists.gentoo.org
Subject: Re: [gentoo-releng] Re: [gentoo-amd64] Re: 2004.0 Profile Deprecated
Date: Mon, 16 Aug 2004 11:10:15 -0400 [thread overview]
Message-ID: <1092669014.8655.44.camel@localhost> (raw)
In-Reply-To: <20040813185828.GA2481@linux1.home>
[-- Attachment #1: Type: text/plain, Size: 1640 bytes --]
On Fri, 2004-08-13 at 14:58, William Hubbs wrote:
> I don't see why we need the yearly refreshes either.
>
> I like the suggestion of making the names more descriptive in stead of using numbers.
> Fore example, default/linux/am64.
> Then, you might have default/linux/am64/gcc34.
> Suppose that you decide to make the default am64 profile use gcc 3.4. All you have to do is merge the am64/gcc34 profile into the am64 profile.
> You could do this type of merging with any revision you want to become part of the default profile, and otherwise not change the default profile at all.
>
> What do you think?
So how does a user know the profile has changed? What happens to users
using the gcc34 profile? What would this do to any of the proposed
"stable" portage tree incarnations?
I'm all for a profile for each release which *never* changes. Additions
can be made as sub-profiles, but a profile never changes. This way
things act exactly the same every time. Consistency is a REQUIREMENT
for QA.
I think creating a profile for each release is very simple. I've
created one myself for 2004.2 and I can tell you that it sure was a hard
3 minutes of my life... *grin*
Having a stable profile is a definite requirement for any stable
project. Since we've been talking with the stable project guys, I think
we definitely should not be discussing doing the exact opposite of what
is needed to cooperate with them, especially on a separate list which
they might not be subscribed to...
--
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 prev parent reply other threads:[~2004-08-16 15:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200408111331.30552.jhuebel@gentoo.org>
[not found] ` <pan.2004.08.12.09.17.55.915519@cox.net>
[not found] ` <200408121001.42258.jhuebel@gentoo.org>
2004-08-12 17:36 ` [gentoo-releng] Re: [gentoo-amd64] Re: 2004.0 Profile Deprecated Paul de Vrieze
2004-08-12 22:05 ` Jason Huebel
2004-08-12 23:20 ` John Davis
2004-08-12 23:36 ` Jason Huebel
2004-08-13 0:52 ` John Davis
2004-08-13 1:08 ` Jason Huebel
2004-08-13 3:29 ` John Davis
[not found] ` <1092375494.17392.1.camel@sephora>
2004-08-13 14:20 ` John Davis
2004-08-13 14:49 ` Jason Huebel
2004-08-13 13:39 ` Aron Griffis
2004-08-13 14:59 ` Jason Huebel
2004-08-13 18:58 ` William Hubbs
2004-08-13 19:08 ` Jason Huebel
2004-08-13 21:22 ` William Hubbs
2004-08-15 1:19 ` John Davis
2004-08-16 15:10 ` Chris Gianelloni [this message]
2004-08-19 15:59 ` John Davis
2004-08-19 17:16 ` Chris Gianelloni
2004-08-19 18:10 ` Ned Ludd
2004-08-19 19:16 ` Chris Gianelloni
2004-08-20 15:09 ` John Davis
2004-08-20 15:40 ` Jason Huebel
2004-08-20 16:20 ` John Davis
2004-08-16 15:00 ` Chris Gianelloni
2004-08-16 22:29 ` William Hubbs
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=1092669014.8655.44.camel@localhost \
--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