From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] Identifying inherit-only / usable profiles (round 2)
Date: Sun, 13 Mar 2005 15:19:33 -0500 [thread overview]
Message-ID: <1110745173.18760.6.camel@vertigo.twi-31o2.org> (raw)
In-Reply-To: <423483AA.8000706@hub.net.nz>
[-- Attachment #1: Type: text/plain, Size: 1355 bytes --]
On Mon, 2005-03-14 at 07:17 +1300, Jerome Brown wrote:
> Wont this cause headaches when it comes to depreciating profiles
> however? If there are very few changes between versions, I can forsee a
> time where someone wants to keep 2004.3, 2005.0, 2005.1, 2006.0, 2006.1,
> 2007.0, 2007.1 around because 2008.0 inherits from 2007.1 which inherits
> from ... (you get the idea). How would this work and how long would you
> be willing to keep a profile around for until it is removed and not just
> depreciated?
Well, we would need to have enough sense to migrate data when we
deprecate. Once we deprecate 2004.3, we would copy the 2004.3 stuff to
2005.0 and break the inheritance on 2004.3 from 2005.0 and so on.
As for deprecation, I think we currently have a loose rule of 6 months
after deprecation for the profile removal.
> (I do think that multiple inheritance is A Good Thing (TM), especially
> if it becomes possible to have user defined profiles in
> /etc/portage/profiles which can inherit from multiple 'base' profiles)
The only real problem with user-provided profiles is the simplicity with
which a user could completely hose their system and our complete lack of
ability to troubleshoot problems with them.
--
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-03-13 20:25 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-27 22:23 [gentoo-dev] Identifying inherit-only / usable profiles (round 2) Aaron Walker
2005-03-01 10:21 ` Aaron Walker
2005-03-01 14:47 ` Chris Gianelloni
2005-03-01 15:07 ` Aaron Walker
2005-03-07 18:42 ` Chris Gianelloni
2005-03-08 14:24 ` Mike Frysinger
2005-03-09 4:56 ` Aaron Walker
2005-03-09 16:46 ` Chris Gianelloni
2005-03-09 23:57 ` Jason Stubbs
2005-03-10 0:49 ` Mike Frysinger
2005-03-10 0:50 ` Mike Frysinger
2005-03-10 1:41 ` Jerome Brown
2005-03-10 12:56 ` Aaron Walker
2005-03-10 15:49 ` Chris Gianelloni
2005-03-10 15:53 ` Ciaran McCreesh
2005-03-10 16:27 ` Chris Gianelloni
2005-03-13 18:17 ` Jerome Brown
2005-03-13 20:19 ` Chris Gianelloni [this message]
2005-03-13 22:05 ` Martin Schlemmer
2005-03-14 14:43 ` Mike Frysinger
2005-03-10 16:55 ` Lina Pezzella
2005-03-30 9:27 ` Aaron Walker
2005-03-30 14:00 ` Chris Gianelloni
2005-04-01 18:50 ` Aaron Walker
2005-04-01 19:31 ` Mike Frysinger
2005-04-01 19:46 ` Chris Gianelloni
2005-04-01 21:02 ` Mike Frysinger
2005-04-02 6:15 ` Aaron Walker
2005-04-02 7:35 ` Jason Stubbs
2005-04-02 16:41 ` Chris Gianelloni
2005-04-02 16:51 ` Daniel Ostrow
2005-04-03 3:55 ` Jason Stubbs
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=1110745173.18760.6.camel@vertigo.twi-31o2.org \
--to=wolf31o2@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@robin.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