From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Deprecate EAPI1?
Date: Sun, 11 Mar 2012 13:01:46 +0100 [thread overview]
Message-ID: <1331467306.11661.2.camel@belkin4> (raw)
[-- Attachment #1: Type: text/plain, Size: 468 bytes --]
After reading previous discussion:
http://help.lockergnome.com/linux/gentoo-dev-Deprecate-EAPIs--ftopict530567.html
Looks like preventing NEW commits from using eapi1 (via repoman) could
be done without major issues. This could even being done also for eapi2
as it's close enough to eapi3, but I don't have a strong opinion about
eapi2 deprecation (personally, I try to always use latest eapi if eclass
allows me to do so).
Any thoughts on this?
Thanks
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2012-03-11 12:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-11 12:01 Pacho Ramos [this message]
2012-03-11 13:28 ` [gentoo-dev] Deprecate EAPI1? Patrick Lauer
2012-03-11 13:52 ` Rich Freeman
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=1331467306.11661.2.camel@belkin4 \
--to=pacho@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