public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tom Wijsman <TomWij@gentoo.org>
To: blueness@gentoo.org
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Tightening EAPI rules
Date: Mon, 10 Feb 2014 15:35:58 +0100	[thread overview]
Message-ID: <20140210153558.66217d33@TOMWIJ-GENTOO> (raw)
In-Reply-To: <52F8D2E7.3030901@gentoo.org>

On Mon, 10 Feb 2014 08:23:51 -0500
"Anthony G. Basile" <blueness@gentoo.org> wrote:

> On 02/10/2014 07:43 AM, Patrick Lauer wrote:
> > EAPI 4 becomes deprecated when/if there's a new EAPI allowed in-tree
> > (EAPI 6, most likely)
> 
> I am concerned about making this a "rule".

Maybe rather a rule with exceptions, or a rather strong recommendation;
as we've seen easier, sometimes a rule needs a revision.

> While I think its okay for the 4/5/6 move, I'm not sure if it will
> always be a good idea. 1) "Deprecating" an EAPI can mean breakage ---
> see my next point. 2) To tie the deprecation of the older EAPI to the
> introduction of a newer one can delay the introduction of the newer
> one and possibly needed features. You will connect the question of
> "are we ready to deprecate X" with the question "we need to introduce
> Y for needed features a, b and c."

It is hard to grasp for me for when features from a newer EAPI would
delay the migration, do you have an example?

> The statement "Deprecating an EAPI can mean breakage" depends on what
> we mean by "deprecating."  I'm assuming here we mean something like
> repoman won't allow commits at EAPI=1,2,3 but that ebuilds in the
> tree at those EAPI's will continue working.  Eg. dosed which was
> deprecated in the EAPI 3 to 4 jump.

Good point, we should probably split this up in multiple phases:

 1) Repoman warns about deprecation of ebuilds with older EAPI.

 2) Repoman bails out on the addition of _new_ ebuilds with older EAPI.

 3) Repoman bails out on changes to _existing_ ebuilds with older EAPI.

As a side note, we'll need to implement VCS diff support in repoman to
check for this; as currently you can only check based the ebuilds.
Nevertheless a hack is possible, but I think we should avoid that...

-- 
With kind regards,

Tom Wijsman (TomWij)
Gentoo Developer

E-mail address  : TomWij@gentoo.org
GPG Public Key  : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2  ABF0 95B2 1FCD 6D34 E57D


  parent reply	other threads:[~2014-02-10 14:36 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-10 12:43 [gentoo-dev] [RFC] Tightening EAPI rules Patrick Lauer
2014-02-10 13:03 ` Dirkjan Ochtman
2014-02-10 13:21   ` Tom Wijsman
2014-02-10 13:24     ` Dirkjan Ochtman
2014-02-10 14:23       ` Tom Wijsman
2014-02-10 14:41         ` Rich Freeman
2014-02-10 14:58           ` Tom Wijsman
2014-02-10 16:16             ` Ciaran McCreesh
2014-02-10 17:08               ` Tom Wijsman
2014-02-10 13:23 ` Anthony G. Basile
2014-02-10 13:46   ` Patrick Lauer
2014-02-10 14:07     ` Rich Freeman
2014-02-10 14:25     ` Ian Stakenvicius
2014-02-10 15:31     ` Ulrich Mueller
2014-02-10 15:42       ` Rich Freeman
2014-02-10 16:05         ` Ulrich Mueller
2014-02-10 16:26           ` Alan McKinnon
2014-02-10 20:56             ` Alec Warner
2014-02-10 21:26               ` Alan McKinnon
2014-02-10 17:20           ` Tom Wijsman
2014-02-10 17:47             ` Rich Freeman
2014-02-10 19:04     ` Lars Wendler
2014-02-10 14:35   ` Tom Wijsman [this message]
2014-02-10 15:34     ` Anthony G. Basile
2014-02-10 13:34 ` Rich Freeman
2014-02-10 13:44   ` Patrick Lauer
2014-02-10 14:52   ` Tom Wijsman
2014-02-12  5:07 ` [gentoo-dev] " Ryan Hill

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=20140210153558.66217d33@TOMWIJ-GENTOO \
    --to=tomwij@gentoo.org \
    --cc=blueness@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