public inbox for gentoo-releng@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jason Huebel <jhuebel@gentoo.org>
To: gentoo-releng@lists.gentoo.org
Subject: Re: [gentoo-releng] Re: [gentoo-amd64] Re: 2004.0 Profile Deprecated
Date: Fri, 13 Aug 2004 14:08:59 -0500	[thread overview]
Message-ID: <200408131409.05606.jhuebel@gentoo.org> (raw)
In-Reply-To: <20040813185828.GA2481@linux1.home>

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

On Friday 13 August 2004 1:58 pm, 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?

Again I'm concerned that there isn't a built-in revision history outside of 
CVS using this method.  Since users don't have CVS access, they don't have a 
convenient way to tell which profile is the "newest".  Since we can't be sure 
that everyone has moved off a particular profile, we have to keep ALL the 
profiles around for an extended period of time.  So not having a revision 
history makes it more difficult to understand what the latest and greatest 
is.

-- 
Jason Huebel
Gentoo/amd64 Strategic Lead
Gentoo Developer Relations/Recruiter

GPG Public Key:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x9BA9E230

"Do not weep; do not wax indignant. Understand."
Baruch Spinoza (1632 - 1677)

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-08-13 19:08 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 [this message]
2004-08-13 21:22                     ` William Hubbs
2004-08-15  1:19                       ` John Davis
2004-08-16 15:10                   ` Chris Gianelloni
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=200408131409.05606.jhuebel@gentoo.org \
    --to=jhuebel@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