From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Deprecate EAPI1?
Date: Sun, 11 Mar 2012 09:52:40 -0400 [thread overview]
Message-ID: <CAGfcS_nRgRTKh=Ks916kbtjsAkFWjZjbOyjtdXAxm97AKHrLdQ@mail.gmail.com> (raw)
In-Reply-To: <4F5CA874.6070209@gentoo.org>
On Sun, Mar 11, 2012 at 9:28 AM, Patrick Lauer <patrick@gentoo.org> wrote:
> I'd deprecate eapi2 too, we don't need 5 flavours around when we
> effectively only want to support one (and eapi0 in a few places)
>
> I wouldn't mind having a deprecation timeline for eapi3 too (now +6
> months maybe?), but there's no need to rush things.
Is there really much of a benefit to this? I guess for anybody who
runs scripts to mass-manipulate ebuilds it might be helpful, but I
think all the package managers planned on supporting all the EAPIs for
quite a while longer.
I can imagine that this will lead to quite a bit of churn with
updating ebuilds and especially eclasses. If a package doesn't
require a feature in a newer EAPI, what is the point?
Why not deprecate the x86 arch while we're at it... :)
Rich
next prev parent reply other threads:[~2012-03-11 13:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-11 12:01 [gentoo-dev] Deprecate EAPI1? Pacho Ramos
2012-03-11 13:28 ` Patrick Lauer
2012-03-11 13:52 ` Rich Freeman [this message]
2012-03-11 13:54 ` Samuli Suominen
2012-03-11 13:55 ` Ciaran McCreesh
2012-03-11 15:14 ` Chí-Thanh Christopher Nguyễn
2012-03-11 15:49 ` Ciaran McCreesh
2012-03-11 16:18 ` Chí-Thanh Christopher Nguyễn
2012-03-11 16:27 ` Ciaran McCreesh
2012-03-11 16:46 ` Chí-Thanh Christopher Nguyễn
2012-03-11 16:52 ` Ciaran McCreesh
2012-03-11 19:04 ` Rich Freeman
2012-03-11 19:11 ` Chí-Thanh Christopher Nguyễn
2012-03-12 0:49 ` Brian Harring
2012-03-13 18:52 ` Zac Medico
2012-03-18 11:17 ` Pacho Ramos
2012-03-15 21:31 ` Maciej Mrozowski
2012-03-11 23:15 ` Francesco Riosa
2012-03-11 14:37 ` Patrick Lauer
2012-03-11 15:02 ` Thomas Sachau
2012-03-12 7:52 ` Pacho Ramos
[not found] <41490c1dd7ca44bcbda73b2032982596@HUBCAS1.cs.stonybrook.edu>
2012-03-11 23:54 ` Richard Yao
2012-03-12 0:15 ` Francesco Riosa
2012-03-12 0:36 ` Rich Freeman
2012-03-12 0:23 ` Chí-Thanh Christopher Nguyễn
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='CAGfcS_nRgRTKh=Ks916kbtjsAkFWjZjbOyjtdXAxm97AKHrLdQ@mail.gmail.com' \
--to=rich0@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