From: Justin <jlec@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: RFC: fortran-2.eclass - Support for bin package system without compiler
Date: Thu, 18 Jul 2013 17:50:24 +0200 [thread overview]
Message-ID: <51E80EC0.1050804@gentoo.org> (raw)
In-Reply-To: <20130718153924.GA14765@comet.hsd1.mn.comcast.net>
[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]
On 18/07/13 17:39, Donnie Berkholz wrote:
> On 10:44 Thu 18 Jul , Justin wrote:
>> +fortran-2_pkg_setup() {
>> + case ${EAPI:-0} in
>> + 0|1|2|3)
>> + eqawarn "Support for EAPI < 4 will be removed from the"
>> + eqawarn "fortran-2.eclass in near future."
>> + eqawarn "Please migrate your package to a higher EAPI"
>> + eqawarn "or file a bug at https://bugs.gentoo.org"
>> + _fortran-2_pkg_setup ;;
>
> It's more useful if you provide a date here (30+ days from the commit)
> after which things are no longer guaranteed to work, versus "near
> future."
>
> I didn't catch it in your original email — have you run a scan to see
> how many ebuilds are affected?
>
I did.
In absolute numbers there per EAPI following consumers
1: 2
2: 24
3: 32
4: 106
5: 71
but there are only 10 packages where there is no version with a
sufficient high EAPI?
Most if not all affected packages are under the control of sci, so that
I can easily manage the transition.
I think I will place the deadline 60 days ahead after committing.
Everybody who likes to see the immediate affect just need to bump the
packages to the correct EAPI?
Justin
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
prev parent reply other threads:[~2013-07-18 15:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 7:07 [gentoo-dev] RFC: fortran-2.eclass - Support for bin package system without compiler Justin
2013-07-18 7:12 ` Michał Górny
2013-07-18 7:28 ` Justin
2013-07-18 8:25 ` [gentoo-dev] " Duncan
2013-07-18 8:44 ` Justin
2013-07-18 15:39 ` Donnie Berkholz
2013-07-18 15:50 ` Justin [this message]
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=51E80EC0.1050804@gentoo.org \
--to=jlec@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