public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Call for agenda items - Council meeting 2018-04-08
Date: Thu, 29 Mar 2018 15:34:05 +0200	[thread overview]
Message-ID: <1522330445.1006.21.camel@gentoo.org> (raw)
In-Reply-To: <23228.52463.901357.194625@a1i15.kph.uni-mainz.de>

W dniu czw, 29.03.2018 o godzinie 13∶24 +0200, użytkownik Ulrich Mueller
napisał:
> > > > > > On Thu, 29 Mar 2018, Michał Górny wrote:
> > Next item: provided that EAPI 7 is approved, we'd have 4 'live' EAPIs
> > in motion [1]. I'd like therefore request the Council to vote on:
> > a. banning EAPI 4 for new ebuilds (and EAPI bumps of existing ebuilds).
> > It has been deprecated on 2015-10-11. In the past, deprecated EAPIs were
> > banned within 11/23 months from deprecation, so we're overdue.
> 
> Fine with me.
> 
> > 2. deprecating EAPI 5. In case of EAPIs 3-4 they were deprecated 4-5
> > years after being added.
> 
> I think a better indicator is the time between support for EAPI n+1 in
> stable Portage, and deprecation of EAPI n (see [1]). Using this, I get
> 37 months for EAPI 2, 35 months for EAPI 3, and 34 months for EAPI 4
> deprecation.
> 
> > EAPI 6 has been added on 2015-11-13, and even toolchain team already
> > uses it, so there's really no reason to use EAPI 5 anymore.
> 
> Stable Portage supports EAPI 6 since 2016-01-17, i.e. since 26 months.
> So we would be somewhat on the early side.

Not that it's less than the supported upgrade path.

> What worries me more is that deprecation of EAPI 5 would apply to
> profiles too. However, all profiles are still at EAPI 5 at this point,
> and I don't see any value in upgrading them to EAPI 6.

That's a fair argument. However:

1. Does deprecation really mean anything in terms of profiles? Even
in the context of EAPI bans we explicitly stated that it affects new
packages and EAPI bumps. I think deprecating it for ebuilds is still
meaningful even if profiles would stay EAPI 5.

2. Do we want to keep profiles EAPI 5 indefinitely? If we consider it
a goal to reduce the number of EAPIs in use, I think it would be
reasonable to bump profiles to EAPI 6 proactively, even if it doesn't
change anything.

> 
> Ulrich
> 
> > [1]:https://wiki.gentoo.org/wiki/Project:Package_Manager_Specification#Council_approval_and_use_in_Gentoo_repository

-- 
Best regards,
Michał Górny



  reply	other threads:[~2018-03-29 13:34 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-27 22:11 [gentoo-project] Call for agenda items - Council meeting 2018-04-08 Matthias Maier
2018-03-28 14:33 ` R0b0t1
2018-03-29 21:55   ` Andreas K. Huettel
2018-03-29  9:52 ` Michał Górny
2018-03-29 11:39   ` Ulrich Mueller
2018-03-31  9:04     ` Ulrich Mueller
2018-03-29 10:13 ` Michał Górny
2018-03-29 11:24   ` Ulrich Mueller
2018-03-29 13:34     ` Michał Górny [this message]
2018-03-29 13:55       ` Ulrich Mueller
2018-03-29 22:00       ` Andreas K. Huettel
2018-03-29 11:46 ` Francisco Blas Izquierdo Riera (klondike)
2018-03-29 11:53   ` Rich Freeman
2018-03-29 13:09     ` Ulrich Mueller
2018-03-29 14:28       ` Francisco Blas Izquierdo Riera (klondike)
2018-03-29 22:02     ` Andreas K. Huettel
2018-03-29 20:26 ` Michał Górny
2018-03-29 22:39 ` Andreas K. Huettel
2018-03-30  5:18   ` Robin H. Johnson
2018-03-30 11:46     ` Rich Freeman
2018-04-02 10:00   ` Michał Górny
2018-04-02 15:43     ` Daniel Robbins
2018-04-02 15:46       ` Matthias Maier
2018-04-02 15:51         ` Daniel Robbins
2018-04-02 16:05       ` Ulrich Mueller
2018-04-02 16:07         ` Daniel Robbins
2018-04-03  3:22     ` R0b0t1
2018-04-04  3:57       ` Gregory Woodbury
2018-04-03  0:40 ` Matthias Maier
2018-04-03  1:01   ` Rich Freeman
2018-04-03  1:14     ` M. J. Everitt
2018-04-03  1:38     ` Matthias Maier
2018-04-03  1:46       ` Rich Freeman
2018-04-06  3:20         ` Robin H. Johnson

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=1522330445.1006.21.camel@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=gentoo-project@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