public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Todd Berman" <tberman@gentoo.org>
To: "'matt c'" <matt@legalizefreedom.org>, <gentoo-dev@gentoo.org>
Subject: RE: [gentoo-dev] Gentoo 1.4 final against rc's
Date: Fri, 15 Aug 2003 13:27:30 -0400	[thread overview]
Message-ID: <005401c36352$81671370$8500a8c0@PROTON> (raw)
In-Reply-To: <003801c3634e$b8475f70$1401a8c0@punx>



> -----Original Message-----
> From: matt c [mailto:matt@legalizefreedom.org]
> Sent: August 15, 2003 1:00 PM
> To: gentoo-dev@gentoo.org
> Subject: Re: [gentoo-dev] Gentoo 1.4 final against rc's
> 
> ----- Original Message -----
> From: "Michael Cummings" <mcummings@gentoo.org>
> Sent: Friday, August 15, 2003 6:11 AM
> Subject: Re: [gentoo-dev] Gentoo 1.4 final against rc's
> 
> 
> > Another 2 cents (can we buy a cup of coffee yet?) -
> >
> > What about "milestone" instead?
> 
> I think this will still cause confusion among the users. Calling
Gentoo
> anything other than Gentoo (even a milestone or a snapshot) is still
> giving
> it a version number. A version number implies that there is something
to
> be
> updated. Sure, the baselayout changes, as does gcc and xfree, etc. But
> this
> is a constantly changing thing - HIGHLY dependant upon your ~arch or
lack
> thereof, and how often you update packages. Users will still think
they
> need
> to "reinstall" or "upgrade" something.
> 
> I think that is the strength of Gentoo - no two installations will
ever be
> even close to the same. How can one put any sort of number on this? By
> versioning the stages, we remove any doubt about what people have -
one
> could say "I installed with Gentoo Stage1-1.4 and I now have a 'Gentoo
> System'." How can one put a version number on my system (which is
> completely
> and utterly different than almost any one elses?) The only thing my
> installation has in common with anyone elses is that I installed from
the
> same stage and stage version as others did.

Not exactly, you are missing a very important thing your installation
had in common with a lot of other peoples.

The Portage Tree.


> Matt
> 
> 
> 
> --
> gentoo-dev@gentoo.org mailing list

Just something to think about :)

-Todd



--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-08-15 17:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-14 19:56 [gentoo-dev] Gentoo 1.4 final against rc's FRLinux
2003-08-14 20:58 ` Spider
2003-08-14 22:20   ` Owen Gunden
2003-08-14 23:08     ` Peter Ruskin
2003-08-15  3:06     ` Zack Gilburd
2003-08-15  6:30       ` C. Brewer
2003-08-15  9:44     ` Camille Huot
2003-08-15  9:54       ` Georgi Georgiev
2003-08-15 10:06         ` Phil Richards
2003-08-15 13:30           ` Chris Gianelloni
2003-08-15 16:41             ` Georgi Georgiev
2003-08-15 11:46         ` William Kenworthy
2003-08-15 13:11       ` Michael Cummings
2003-08-15 17:00         ` matt c
2003-08-15 17:27           ` Todd Berman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-08-15 17:39 matt c
2003-08-15 17:47 ` Todd Berman
2003-08-15 18:10   ` 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='005401c36352$81671370$8500a8c0@PROTON' \
    --to=tberman@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=matt@legalizefreedom.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