public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Fuper <futurist@directvinternet.com>
To: gentoo-dev@gentoo.org
Subject: RE: [gentoo-dev] making %95 of users happy
Date: 19 Apr 2002 09:15:00 -0500	[thread overview]
Message-ID: <1019225702.4087.12.camel@silver.perimeter> (raw)
In-Reply-To: <NCEBJBHELIGGHDDGAEGNEEGHDJAA.wylie@geekasylum.org>

On Fri, 2002-04-19 at 07:04, Todd Wright wrote:
> > > > And to the person (Andrew I think) who quoted the following 
> > from the gentoo site as a reason for not having release branches...
> > > > 
> > > > "*Portage allows you to set up Gentoo Linux the way you like it*..."
> > > > 
> > > > It doesnt. Just when I get it how I like it, it changes.
> > 
> > "IT changes"??  I'm at a loss here.  You mean that YOU keep telling it
> > to change?  <wink>  I think that you missed Daniel Robbins point:
> 
> Perhaps this will work itself out all by itself.
> When Gentoo 1.2 is released and the make.profile is changed to point at the default-1.2 profile
> the bleeding edgers can use that while the more conservative keep their link to 1.0  
> Thinking about it, this is probably the ultimate solution, 
> its just not apparent right now since Gentoo is so young, and the only
> available option is to use the 1.0 profile. When there is a choice,
> the current version profile will be bleeding edge, while the previous
> version will only be updated with major fixes, and will become the 
> "stable" release.
> 
> There. I've just convinced myself. This is a temporary problem that solves itself as Gentoo matures.

You've convinced me too.

I think that some of the concerns and proposals reflect a belief that
Gentoo keeps changing and therefore can not survive.  That has been
Microsoft's argument against Linux itself.  My argument is that by
extending our control loop back further in the process, all the way back
to the source codes, we have created an inherently stable system (there
will be perturbations but we will always recover).  The alternative
being proposed is like the formalizations of the Debian release
procedure, and notice that Debian is having a hard time getting a stable
release of Woody (and that Woody still uses the 2.2 kernel by default).






  parent reply	other threads:[~2002-04-19 14:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-18 12:25 [gentoo-dev] making %95 of users happy Gaarde
2002-04-18 18:29 ` Todd Wright
2002-04-18 19:28   ` Stefan Boresch
2002-04-19  3:25     ` Fuper
2002-04-19 12:04       ` Todd Wright
2002-04-18 22:09         ` Sherman Boyd
2002-04-19 14:15         ` Fuper [this message]
2002-04-18 19:35   ` Terje Kvernes
2002-04-19  8:42     ` Paul de Vrieze
2002-04-19  9:44       ` Terje Kvernes
2002-04-19 10:19         ` Einar Karttunen
2002-04-19 11:34           ` Mike Payson
  -- strict thread matches above, loose matches on Subject: below --
2002-04-19 17:57 Gaarde
2002-04-20  0:30 ` John White
2002-04-20 18:26 Gaarde

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=1019225702.4087.12.camel@silver.perimeter \
    --to=futurist@directvinternet.com \
    --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