public inbox for gentoo-releng@lists.gentoo.org
 help / color / mirror / Atom feed
From: John Davis <zhen@gentoo.org>
To: seemant@gentoo.org
Cc: gentoo-releng@lists.gentoo.org
Subject: Re: [gentoo-releng] Re: [gentoo-amd64] Re: 2004.0 Profile Deprecated
Date: Fri, 13 Aug 2004 10:20:29 -0400	[thread overview]
Message-ID: <1092406829.30635.37.camel@woot.uberdavis.com> (raw)
In-Reply-To: <1092375494.17392.1.camel@sephora>

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

On Fri, 2004-08-13 at 01:38, Seemant Kulleen wrote:
> you know, this maybe silly, but I do kind of like not having version
> numbers at all, and maybe making the profile names more descriptive
> 
> so in the amd64 profile, you'd have gcc34, for example
> and in all of them, we could have xfree and xorg profiles.
>   Thoughts?

I could see either way working. The nice thing about your proposal is
that it cuts all of the bloat associated with version numbering. The
only con that I can see is that it does not offer a standardized way of
marking profile revisions like jhuebel's does (-r1, -r2, no matter what
the arch or the change).

Since this is a good comment, I am forwarding it to the list ;)

Regards,
-- 
John Davis
Gentoo Linux Developer
<http://dev.gentoo.org/~zhen>

----
GnuPG Public Key: <http://dev.gentoo.org/~zhen/zhen_pub.asc>
Fingerprint: 4F9E 41F6 D072 5C1A 636C  2D46 B92C 4823 E281 41BB

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

  parent reply	other threads:[~2004-08-13 14:20 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 [this message]
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
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=1092406829.30635.37.camel@woot.uberdavis.com \
    --to=zhen@gentoo.org \
    --cc=gentoo-releng@lists.gentoo.org \
    --cc=seemant@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