public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Harring <ferringb@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Deprecate EAPI1?
Date: Sun, 11 Mar 2012 17:49:35 -0700	[thread overview]
Message-ID: <20120312004935.GB7579@localhost> (raw)
In-Reply-To: <4F5CC159.1020602@gentoo.org>

On Sun, Mar 11, 2012 at 04:14:33PM +0100, Ch??-Thanh Christopher Nguy???n wrote:
> Ciaran McCreesh schrieb:
> >> 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.
> > We have to support them indefinitely. It's not possible to uninstall a
> > package whose EAPI is unknown.
> >
> 
> Would it be feasible to do a pkg_pretend() check and refuse
> install/upgrade if packages with unsupported EAPI  are detected?

The question should be "is it worth doing it", rather than "can we 
hack out something".

As Ciaran said, PM's are going to be supporting EAPI1 indefinitely- 
it's zero cost to do so at this point.  Thus doing what you're 
proposing doesn't gain us anything but complexity.

If people want to enforce the eapi1 is no longer used in the gentoo 
repo, that's fine- we stick a list of acceptable EAPI's into 
its layout.conf.

If you want to block EAPI1 from being further used, go that route; at 
least for pkgcore (and presumably paludis, likely portage), ripping 
out EAPI1 is unlikely to occur anything this side of 2015.

~brian



  parent reply	other threads:[~2012-03-12  0:50 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
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 [this message]
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=20120312004935.GB7579@localhost \
    --to=ferringb@gmail.com \
    --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