>>>>> On Thu, 11 Jun 2015, Jason Zaman wrote:

> This would be great! Do we have a list somewhere of ebuilds that are
> still EAPI1? and which of those have a newer version that is a
> higher EAPI for the same keywords? IE how many of the EAPI1 ebuilds
> cant just be dropped?
>>>>> On Thu, 11 Jun 2015, Alexis Ballier wrote:

> are those 60 ebuilds best visible ones ?
> better convert the last few remaining so that best visible one is
> not eapi1 before banning it

Here is the list, with the second column indicating if the ebuild in
question is the best version of its package (or of its slot).

    app-i18n/atokx2-17.0                    no
    app-i18n/atokx2-17.0-r2                 yes
    app-i18n/im-freewnn-0.0.2-r1            yes
    app-i18n/scim-input-pad-0.1.1           no
    app-i18n/x-unikey-1.0.4-r1              no
    dev-java/aspectwerkz-2.0_rc2-r3         no
    dev-java/bcmail-1.38-r3                 in slot
    dev-java/bsf-2.4.0-r1                   yes
    dev-java/burlap-3.0.8-r3                yes
    dev-java/caucho-services-3.0.8-r2       yes
    dev-java/commons-configuration-1.6      no
    dev-java/commons-configuration-1.6-r1   yes
    dev-java/commons-jxpath-1.3             no
    dev-java/commons-lang-2.6               in slot
    dev-java/commons-logging-1.1.1          no
    dev-java/commons-modeler-2.0.1          yes
    dev-java/dom4j-1.6.1-r3                 no
    dev-java/exolabcore-0.3.7_p20050205-r2  yes
    dev-java/hessian-3.0.8-r5               in slot
    dev-java/hessian-3.0.20                 in slot
    dev-java/hessian-3.1.6                  in slot
    dev-java/hessian-4.0.3                  yes
    dev-java/java-dep-check-0.3             yes
    dev-java/jaxb-2.1.2-r1                  yes
    dev-java/jaxb-tools-2.1.2               yes
    dev-java/jax-ws-tools-2.0.1-r1          yes
    dev-java/jcs-1.2.7.9-r1                 in slot
    dev-java/jcs-1.3-r1                     yes
    dev-java/jpf-1.5.1                      yes
    dev-java/jpfcodegen-0.4                 yes
    dev-java/jsr101-1.4-r1                  no
    dev-java/jython-2.2.1-r1                no
    dev-java/msv-20050627-r2                no
    dev-java/msv-20050627-r3                yes
    dev-java/mx4j-3.0.1-r4                  no
    dev-java/mx4j-tools-3.0.1-r2            no
    dev-java/mx4j-tools-3.0.2               yes
    dev-java/pdfbox-0.7.3-r3                in slot
    dev-java/poi-3.0.2-r1                   in slot
    dev-java/poi-3.2                        yes
    dev-java/rhino-1.7.2-r2                 yes
    dev-java/ws-commons-util-1.0.1          yes
    dev-java/wstx-3.2.8                     no
    dev-java/xalan-2.7.1                    yes
    dev-java/xmlgraphics-commons-1.3.1      in slot
    dev-java/xpp2-2.1.10-r1                 yes
    dev-java/xstream-1.3.1-r1               no
    dev-lang/ocaml-3.12.1                   in slot
    dev-scheme/gauche-gtk-0.4.1             no
    gpe-base/gpe-icons-0.25                 masked for removal
    gpe-base/libgpepimc-0.9                 masked for removal
    media-sound/audacious-2.4.4             no
    media-tv/xawtv-3.95-r2                  no
    net-ftp/gftp-2.0.19-r1                  no
    net-ftp/gproftpd-8.3.2                  no
    sci-biology/emboss-6.0.1                no
    x11-misc/matchbox-panel-manager-0.1     yes
    x11-misc/pathfinder-1.6.36              no
    x11-misc/shutterbug-1.6.36              no

This leaves us with 4 ebuilds outside of the dev-java category which
are the newest of their package or slot. Since chewi has acknowledged
it for dev-java, I have committed the change to layout.conf now.

> my bet would be that those 60 ebuilds are from packages barely
> maintained, and i doubt banning their eapi will improve that, rather
> the contrary

Maintainers can still use --force if there is no other way.

Ulrich

Attachment: pgpW_tLoUIFgx.pgp
Description: PGP signature

Reply via email to