public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] GRP set consolidation
Date: Fri, 21 May 2004 18:11:58 -0400	[thread overview]
Message-ID: <1085177518.25042.126.camel@localhost> (raw)
In-Reply-To: <40AE75D1.4010401@gentoo.org>

On Fri, 2004-05-21 at 17:34, Joshua Brindle wrote:
> Ok, we just had a conversation in #gentoo-dev and it seems most people 
> are interested in this. The problem as it stands is that our mirrors are 
>   low on space and so other projects can't get space, such as embedded, 
> hardened and even other archs. The main user of space is having 5 grp 
> packagecd's for x86 alone. The idea is to build a consolidated grp set 
> with a generic -mcpu (i686 or so) and then use that.
> 
> As I'm sure this will become a large and flaming thread, and probably 
> won't read them all I'll just go ahead and suggest that we add this to 
> the next meeting to discuss it if there are large amounts of disagreement.

Just to reiterate what I had said on -dev, I think it is a good idea. 
I'm not either "for" or "against" it, I just think having only one set
of packages to QA would make all our lives easier.  I *can* see the need
for 2 GRP sets, perhaps a x86 and a i686 set, simply to please the users
that find GRP useful.

The other take on this is gentoopix and what it will provide.  If it can
provide the same functionality as doing a GRP install, then I would say
we need to get moving on gentoopix and get rid of GRP (but not before).

Just my .02c

-- 
Chris Gianelloni
Developer
Games/LiveCD Teams
Gentoo Linux

Is your power animal a penguin?


--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2004-05-21 22:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-21 21:34 [gentoo-dev] GRP set consolidation Joshua Brindle
2004-05-21 22:11 ` Chris Gianelloni [this message]
2004-05-21 22:09   ` Stuart Herbert
2004-05-21 23:41     ` Pieter Van den Abeele
2004-05-22  0:01       ` John Davis
2004-05-22  0:08         ` Joseph Booker
2004-05-22  0:48           ` John Davis
2004-05-22  1:11             ` Joseph Booker
2004-05-22  0:44         ` Pieter Van den Abeele
2004-05-23 11:04     ` Kurt Lieber
2004-05-21 22:14 ` Ciaran McCreesh
2004-05-21 23:15 ` John Davis
2004-05-22 20:37   ` Nick Rout

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=1085177518.25042.126.camel@localhost \
    --to=wolf31o2@gentoo.org \
    --cc=gentoo-dev@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