В Чтв, 14/02/2008 в 02:10 +0200, Mart Raudsepp пишет:
> On K, 2008-02-13 at 15:49 -0500, Doug Klima wrote:
> > 
> >     deprecated eclasses:64-bit, darcs, db4-fix, debian, embassy-2.10,
> >     embassy-2.9, gcc, gnustep-old, gtk-engines, gtk-engines2, inherit,
> >     jakarta-commons, java-pkg, java-utils, kde-base, kde-i18n, kde-source,
> >     kmod, koffice-i18n, motif, mozilla, myth, pcmcia, perl-post, php, php-2,
> >     php-ext, php-ext-base, php-ext-pecl, php-ext-source, php-lib, php-pear,
> >     php-sapi, php5-sapi, php5-sapi-r1, php5-sapi-r2, php5-sapi-r3, tla,
> >     webapp-apache, xfree
> > 
> > Missing from that list is kernel and gst-plugins.
> 
> wxlib also.
> Do I need to be adding deprecation notice somewhere? I didn't see
> anything in some of the listed above eclasses

Some of them are not used in the tree any more:

64-bit db4-fix debian embassy-2.10 embassy-2.9 gcc gnustep-old
gtk-engines gtk-engines2 jakarta-commons java-utils kde-base kde-i18n
kde-source kmod koffice-i18n motif mozilla myth pcmcia perl-post php
php-2 php-ext php-ext-base php-ext-pecl php-ext-source php-lib
php-pearphp-sapi php5-sapi php5-sapi-r1 php5-sapi-r2 php5-sapi-r3 tla
webapp-apache xfree gst-plugins wxlib

May be we should punt them from the tree?

And some are used by small number of packages:

darcs
dev-lisp/cl-fiveam-darcs/cl-fiveam-darcs-20060825.ebuild
dev-lisp/cl-arnesi-darcs/cl-arnesi-darcs-20060825.ebuild
dev-lisp/cl-rfc2388-darcs/cl-rfc2388-darcs-20060825.ebuild
dev-lisp/cl-rfc2109-darcs/cl-rfc2109-darcs-20060825.ebuild
dev-lisp/cl-parenscript-darcs/cl-parenscript-darcs-20060825.ebuild
dev-lisp/cl-yaclml-darcs/cl-yaclml-darcs-20060825.ebuild

kernel
sys-kernel/mips-sources/mips-sources-2.6.23.14.ebuild
sys-kernel/mips-sources/mips-sources-2.6.20.18.ebuild
sys-kernel/mips-sources/mips-sources-2.6.22.6.ebuild
sys-kernel/mips-headers/mips-headers-2.4.28-r1.ebuild

java-pkg - is it deprecated? Reading comments inside java eclass it's
hard to say that.

inherit - I did not found ebuilds where it is used, but actually I do
not know how it was used, so may be I overlooked something.

The check was done with the following script:

find /usr/portage \( -name '*.ebuild' -o -name '*.eclass' \) \
-exec awk "/inherit.*[[:blank:]]+${eclass}([[:blank:]]+.*|$+)/{print FILENAME 
}" \{\} \;

For inherit eclass I've searched manually.

-- 
Peter.

Attachment: signature.asc
Description: Эта часть сообщения подписана цифровой подписью

Reply via email to