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