From: Dylan Carlson <absinthe@gentoo.org>
To: gentoo-dev List <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Policy for retirement of old gentoo 'versions'
Date: Fri, 2 Jul 2004 11:15:11 -0400 [thread overview]
Message-ID: <200407021115.11869.absinthe@gentoo.org> (raw)
In-Reply-To: <20040702144117.GA11463@violet.grantgoodyear.org>
On Friday 02 July 2004 10:41 am, Grant Goodyear wrote:
> I'm probably missing something obvious, but even reading the original
> bug report leaves me confused as to how a lack of stable mm-sources
> ebuilds is breaking systems. Once mm-sources is installed anything
> that needs a kernel tree should build just fine.
I think the problem comes in is if you have done exhaustive testing against
a specific profile, and subsequently want to deploy a series of new
systems using that profile-- which worked at one time, but now is broken
in one way or another because ebuilds were taken out of the tree. This
scenario is one of those "enterprise" problems, but one that I think could
be solved through repoman checks. Unless I'm completely mistaken about
what's being discussed here.
Cheers,
Dylan Carlson [absinthe@gentoo.org]
Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x708E165F
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-07-02 15:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-02 1:20 [gentoo-dev] Policy for retirement of old gentoo "versions" Barry Shaw
2004-07-02 2:17 ` [gentoo-dev] Policy for retirement of old gentoo 'versions' Donnie Berkholz
2004-07-02 12:48 ` Chris Gianelloni
2004-07-02 13:44 ` William Kenworthy
2004-07-02 14:41 ` Grant Goodyear
2004-07-02 15:15 ` Dylan Carlson [this message]
2004-07-02 20:29 ` Chris Gianelloni
2004-07-02 21:06 ` Dylan Carlson
2004-07-02 21:37 ` Chris Gianelloni
2004-07-03 6:34 ` Dylan Carlson
2004-07-04 22:10 ` Marius Mauch
2004-07-05 1:14 ` Dylan Carlson
2004-07-04 22:16 ` Barry Shaw
2004-07-05 1:01 ` Dylan Carlson
2004-07-05 2:19 ` Barry Shaw
2004-07-02 20:21 ` Chris Gianelloni
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=200407021115.11869.absinthe@gentoo.org \
--to=absinthe@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