From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Re: Cutting down on non-cascaded profiles
Date: Tue, 03 May 2005 11:37:47 -0700 [thread overview]
Message-ID: <pan.2005.05.03.18.37.46.556038@cox.net> (raw)
In-Reply-To: 1115136614.889.281.camel@cgianelloni.nuvox.net
Chris Gianelloni posted <1115136614.889.281.camel@cgianelloni.nuvox.net>,
excerpted below, on Tue, 03 May 2005 12:10:14 -0400:
> I think an easier solution would be a portage rescue set of profiles.
> These would be minimal profiles not designed for actual use, but only for
> performing a portage update for those people that lag too far behind. The
> idea would be a very tiny profile, per arch, that is not cascaded.
I like! In some cases, they may be combine-able, as well multiple archs
to a profile, if they are sufficiently minimal. They could remain for
some time to point people to if/as necessary.
My idea for an archive was that this should be pretty low traffic, and
would get it off the rsync mirrors and clean out the profile tree, making
things less confusing. However, put them in a single "emergency-profile"
subtree, and make them tiny enough, and it would do almost as well, while
at the same time still being conveniently located in the portage tree.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-05-03 18:41 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-01 10:17 [gentoo-dev] Cutting down on non-cascaded profiles Donnie Berkholz
2005-05-01 10:35 ` Stuart Longland
2005-05-01 12:31 ` [gentoo-dev] " Duncan
2005-05-01 13:15 ` Ned Ludd
2005-05-02 14:55 ` [gentoo-dev] " Jan Kundrát
2005-05-02 15:53 ` Stephen P. Becker
2005-05-02 16:11 ` Jan Kundrát
2005-05-02 16:33 ` Stephen P. Becker
2005-05-02 16:40 ` Jan Kundrát
2005-05-02 23:55 ` Stuart Longland
2005-05-03 0:45 ` Alec Warner
2005-05-03 0:54 ` Mike Frysinger
2005-05-03 1:31 ` Alec Warner
2005-05-03 6:29 ` Jan Kundrát
2005-05-03 7:05 ` Stuart Longland
2005-05-03 12:27 ` Mike Frysinger
2005-05-03 15:21 ` [gentoo-dev] " Duncan
2005-05-03 16:10 ` Chris Gianelloni
2005-05-03 18:37 ` Duncan [this message]
2005-05-03 18:49 ` Mike Frysinger
2005-05-03 21:05 ` Chris Gianelloni
2005-05-09 20:12 ` Paul de Vrieze
2005-05-09 20:27 ` Mike Frysinger
2005-05-10 9:15 ` Paul de Vrieze
2005-05-10 9:31 ` Georgi Georgiev
2005-05-09 22:23 ` Brian Harring
2005-05-03 21:20 ` Marius Mauch
2005-05-04 7:17 ` John Myers
2005-05-01 11:37 ` [gentoo-dev] " Ned Ludd
2005-05-01 17:11 ` Mike Frysinger
2005-05-02 13:47 ` Chris Gianelloni
2005-05-03 8:53 ` Aaron Walker
2005-05-03 12:43 ` Jason Stubbs
2005-05-03 13:19 ` 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=pan.2005.05.03.18.37.46.556038@cox.net \
--to=1i5t5.duncan@cox.net \
--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