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 ML'" <gentoo-dev@gentoo.org>
Subject: RE: [gentoo-dev] Gentoo 1.4 final against rc's
Date: Fri, 15 Aug 2003 13:47:05 -0400	[thread overview]
Message-ID: <005c01c36355$3dc1d8f0$8500a8c0@PROTON> (raw)
In-Reply-To: <00a801c36354$3ccce710$1401a8c0@punx>


>> Not exactly, you are missing a very important thing your installation
>> had in common with a lot of other peoples.
>>
>> The Portage Tree.
>> Just something to think about :)

>I think you're missing something though -  my system (and your system)
also
>have gcc and python and all the neat gnu utilities like awk, and grep,
and
>bash, etc. These are all *different versions* depending on when you
>last --updated them. The portage tree is also *VERY* different based on
when
>you last ran emerge sync - it changes hourly. My portage tree is
different
>than someone who syncd this AM (as I have not done so for about two
weeks,
>my ram blew up! waiting on RMA.:-(  ) The absolute lowest common
denominator
>that anyone has is the product they installed from - which are the
various
>stages..

Its not so much that I'm missing that, and more that I am attempting to
introduce a different concept of what might quantify a Gentoo 'Release'.

If the 'Release' was based on a snapshot of the Portage Tree (with
security fixes backported of course, most likely major bug fixes as
well), then there would be something uniform and standard to release
against.

--Todd
 


--
gentoo-dev@gentoo.org mailing list


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

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-15 17:39 [gentoo-dev] Gentoo 1.4 final against rc's matt c
2003-08-15 17:47 ` Todd Berman [this message]
2003-08-15 18:10   ` Paul de Vrieze
  -- strict thread matches above, loose matches on Subject: below --
2003-08-14 19:56 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

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='005c01c36355$3dc1d8f0$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