public inbox for gentoo-releng@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaranm@gentoo.org>
To: gentoo-releng@lists.gentoo.org
Subject: Re: [gentoo-releng] Gentoo 2004.1 Release
Date: Thu, 29 Apr 2004 03:24:10 +0100	[thread overview]
Message-ID: <20040429032410.4062e2ef@snowdrop.home> (raw)
In-Reply-To: <40906502.3070607@gentoo.org>

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

On Wed, 28 Apr 2004 23:14:26 -0300 Gustavo Zacarias
<gustavoz@gentoo.org> wrote:
| By this time i may have had more than enough drinks, but wouldn't it
| be useful to handle a separate GRP profile? (or cascading profile).
| I mean, the basic profiles are skinny USE-wise and we (i) don't want
| to get them hogged... some source-building users mostly want to add
| stuff rather than remove, and it's logical. We should add some extras
| for GRPs somehow so they can get some goodies/features they lack
| because of the USE flags.

Hrm, that'd also allow us to lock down to specific glibc, gcc, perl,
openssl, etc. versions just for GRP. That would mostly remove one of the
big problems with GRP as it stands, and move us towards a redhat kind of
model for binaries.

-- 
Ciaran McCreesh, Gentoo XMLcracy Member G03X276
(Sparc, MIPS, Vim, si hoc legere scis nimium eruditionis habes)
Mail:    ciaranm at gentoo.org
Web:     http://dev.gentoo.org/~ciaranm


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

  reply	other threads:[~2004-04-29  2:25 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-28  3:52 [gentoo-releng] Gentoo 2004.1 Release John Davis
2004-04-28 21:36 ` Nathaniel McCallum
2004-04-28 21:52   ` Kurt Lieber
2004-04-28 21:58     ` John Davis
2004-04-28 23:00       ` Donnie Berkholz
2004-04-28 23:26         ` Pieter Van den Abeele
2004-04-29 19:12           ` Sven Vermeulen
2004-04-28 23:01       ` Pieter Van den Abeele
2004-04-28 23:09       ` Ciaran McCreesh
2004-04-28 23:33       ` Kurt Lieber
2004-04-28 23:38         ` John Davis
2004-04-29 19:17           ` Sven Vermeulen
2004-04-29 20:13             ` John Davis
2004-04-29  0:22         ` Daniel Robbins
2004-04-29  0:58           ` Ciaran McCreesh
2004-04-29  1:19             ` John Davis
2004-04-29  2:14               ` Gustavo Zacarias
2004-04-29  2:24                 ` Ciaran McCreesh [this message]
2004-04-29  2:25                 ` Nathaniel McCallum
2004-04-29  2:29                   ` Nathaniel McCallum
2004-04-29  2:32             ` Daniel Robbins
2004-04-29 19:25               ` Sven Vermeulen
2004-04-29 19:16         ` Sven Vermeulen
2004-04-29 19:40           ` Daniel Robbins
2004-04-29 19:46             ` Ciaran McCreesh
2004-04-29 20:12               ` Daniel Robbins
2004-04-29 20:17                 ` John Davis
2004-04-30 14:32                 ` Paul de Vrieze
2004-04-30 15:16                   ` Nathaniel McCallum
2004-04-30 15:35                     ` Sven Vermeulen
2004-04-30 15:50                     ` Paul de Vrieze
2004-04-30 15:55                       ` Nathaniel McCallum
2004-04-29 19:47             ` 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=20040429032410.4062e2ef@snowdrop.home \
    --to=ciaranm@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