From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Council meeting: Tuesday 14 August 2012, 19:00 UTC
Date: Wed, 15 Aug 2012 00:21:55 +0200 [thread overview]
Message-ID: <201208150022.00567.dilfridge@gentoo.org> (raw)
In-Reply-To: <502AC963.5040000@gentoo.org>
[-- Attachment #1: Type: Text/Plain, Size: 1299 bytes --]
Am Dienstag, 14. August 2012, 23:55:47 schrieb Zac Medico:
> It seems like there's some confusion here. Approving a new EAPI and
> deciding to use a new EAPI in a given profile are two entirely different
> things. If we want to us a new EAPI in a profile, we just have to deploy
> it such that users are only exposed to that profile when they
> consciously running `eselect profile` (and they can always revert back
> to the previous profile if it turns out that their installed package
> manager doesn't support the new profile).
Yeah but... either
1) we use such an obscure profile that noone actually notices the change, or
2) we try to change something in the "big, well-known profiles",
and then we're back at the start.
So what good is including a feature in a new profile if there is no way to
make it visible to "the users" in general?
Also, in this particular case, "stable use masking" is useful because it makes
stabilization possible/simpler in cases where otherwise this would lead to
broken dependencies (stable depending on ~arch). If only one small sub-profile
provides the feature, we lose its whole advantage.
--
Andreas K. Huettel
Gentoo Linux developer
kde (team lead), sci, tex, arm, printing
dilfridge@gentoo.org
http://www.akhuettel.de/
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-08-15 0:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 19:17 [gentoo-project] Council meeting: Tuesday 14 August 2012, 19:00 UTC Fabian Groffen
2012-08-12 21:05 ` Ulrich Mueller
2012-08-12 21:13 ` Michał Górny
2012-08-13 7:41 ` hasufell
2012-08-14 7:02 ` Arfrever Frehtes Taifersar Arahesis
2012-08-14 9:24 ` Ciaran McCreesh
2012-08-14 8:15 ` Michał Górny
2012-08-14 9:02 ` Zac Medico
2012-08-14 14:01 ` Ulrich Mueller
2012-08-14 16:09 ` Richard Yao
2012-08-14 16:42 ` Richard Yao
2012-08-14 21:17 ` Andreas K. Huettel
2012-08-14 21:35 ` Ciaran McCreesh
2012-08-14 21:55 ` Zac Medico
2012-08-14 22:02 ` Ciaran McCreesh
2012-08-14 22:14 ` Zac Medico
2012-08-14 22:20 ` Michał Górny
[not found] ` <20120815130131.1a3f10a8@googlemail.com>
2012-08-15 12:11 ` Michał Górny
2012-08-15 12:12 ` Ciaran McCreesh
2012-08-15 12:23 ` Michał Górny
2012-09-08 13:12 ` David Leverton
2012-09-26 23:16 ` Brian Harring
2012-08-14 22:21 ` Andreas K. Huettel [this message]
2012-08-14 22:29 ` Zac Medico
2012-08-26 11:37 ` [gentoo-project] Council meeting summary: " Fabian Groffen
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=201208150022.00567.dilfridge@gentoo.org \
--to=dilfridge@gentoo.org \
--cc=gentoo-project@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