public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: brad@gentoo.org
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Gentoo 1.4.1 and GRP
Date: 15 Sep 2003 12:36:01 -0400	[thread overview]
Message-ID: <1063643761.2993.50.camel@localhost> (raw)
In-Reply-To: <1063641562.12338.7.camel@Discovery.brad-x.com>

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

On Mon, 2003-09-15 at 11:59, Brad Laue wrote:
> Greetings all,
> 
> A concern of mine about many Linux distributions is that in the long
> haul between binary releases of a distribution, the packages included
> with the release can become quite old. In Gentoo's case, if one GRP
> installed their system nine months from now and emerge -u'd, they would
> be faced with a considerable number of packages to update (I wouldn't be
> surprised if it was all of them).
> 
> The Gentoo 1.4.1 release re-ignited my curiosity on this topic. Will
> there be regular interim releases between major upgrades, or will
> releases like these solely fix bugs?
> 
> If the latter, can a GRP ISO be created say, every two months? This
> would only add ~500MB per architecture involved, since there wouldn't be
> any need to archive the older versions of the ISO.
> 
> Realising that Gentoo is of course a source-based distribution, quickly
> and easily installing the latest and greatest by using emerge -k, then
> optimizing by rebuilding incrementally has surely sparked a great deal
> of additional interest in the distribution.
> 
> What does everyone think?

It sounds great, but I think we're battling now with a problem of us
taking up way too much space on our mirrors.  In fact, there is a thread
discussing the removal of the ISO images.

-- 
Chris Gianelloni
Developer, Gentoo Linux
Games Team

Is your power animal a pengiun?

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

  reply	other threads:[~2003-09-15 16:38 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-15 15:59 [gentoo-dev] Gentoo 1.4.1 and GRP Brad Laue
2003-09-15 16:36 ` Chris Gianelloni [this message]
2003-09-15 16:52 ` Luke-Jr
2003-09-15 17:08   ` Chris Gianelloni
2003-09-15 17:20     ` Brad Laue
2003-09-15 17:48       ` Brian Jackson
2003-09-15 18:29         ` Brad Laue
2003-09-15 21:01           ` Philippe Lafoucrière
     [not found]         ` <1063649926.13582.2.camel@Discovery.brad-x.com>
2003-09-16 21:20           ` Brian Jackson
2003-09-17 15:37             ` Sven Vermeulen
2003-09-15 18:04 ` Sven Vermeulen
2003-09-15 18:30   ` Brad Laue
2003-09-15 18:39     ` Sven Vermeulen
2003-09-15 18:53       ` Jon Portnoy
2003-09-15 19:05       ` Brad Laue
2003-09-15 19:06         ` Jon Portnoy
2003-09-15 20:18           ` Brad Laue
2003-09-15 21:16             ` Philippe Lafoucrière
2003-09-15 19:10         ` Sven Vermeulen
2003-09-16 16:34           ` Alexander Gretencord
2003-09-17  5:45             ` Patrick Kursawe
2003-09-15 18:38   ` Andrew Gaffney
2003-09-15 18:42     ` Sven Vermeulen
2003-09-15 21:09       ` Philippe Lafoucrière
2003-09-15 23:33 ` Sven Blumenstein
  -- strict thread matches above, loose matches on Subject: below --
2003-09-15 22:15 Thomas Schweikle
2003-09-15 22:49 ` donnie berkholz
2003-09-15 23:05   ` Marius Mauch
2003-09-16  3:54   ` Matt Thrailkill

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