From: Zac Medico <zmedico@gentoo.org>
To: gentoo-project@lists.gentoo.org,
"Michał Górny" <mgorny@gentoo.org>,
chainsaw@gentoo.org, gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-project] Call for agenda items -- Council meeting 2013-01-08
Date: Thu, 27 Dec 2012 12:41:08 -0800 [thread overview]
Message-ID: <50DCB264.4050403@gentoo.org> (raw)
In-Reply-To: <20121227143738.4d5ce2dd@pomiocik.lan>
On 12/27/2012 05:37 AM, Michał Górny wrote:
> EAPI 5 provides use.stable.mask files to solve this but those files
> require profiles to be EAPI 5. Therefore, in order to be able to use it
> we would have to actually break the update path for older portage
> versions completely.
So, adding new profiles and deprecating the old ones is considered to
"break the update path for older versions"? I don't a problem with
deprecating profiles and forcing users to switch. The only manual labor
involved could be `emerge -1 portage && eselect profile set <target>`.
> I have tried to raise the topic on the mailing list [1] but it mostly
> resulted in some people agreeing that it is an issue that should be
> addressed but no real ideas.
>
> I have come up with three possible solutions myself. Long story short:
>
> a) adding new profiles which will require EAPI=5 and requiring all
> users to migrate to them after upgrading portage. Using new
> use.stable.mask files in those profiles.
This was my plan all along, and seems perfectly reasonable to me.
--
Thanks,
Zac
next prev parent reply other threads:[~2012-12-27 21:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-26 16:42 [gentoo-project] Call for agenda items -- Council meeting 2013-01-08 Tony "Chainsaw" Vroon
2012-12-27 13:37 ` Michał Górny
2012-12-27 15:21 ` Andreas K. Huettel
2012-12-27 20:52 ` Michał Górny
2012-12-27 19:56 ` Ciaran McCreesh
2012-12-27 20:54 ` Michał Górny
2012-12-27 20:41 ` Zac Medico [this message]
2012-12-27 20:55 ` Michał Górny
2013-02-05 22:03 ` [gentoo-project] Preliminary agenda -- Council meeting 2013-02-12 Tony "Chainsaw" Vroon
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=50DCB264.4050403@gentoo.org \
--to=zmedico@gentoo.org \
--cc=chainsaw@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
--cc=mgorny@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