From: Peter Volkov <pva@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] clean deprecated eclasses(?) (was: missing quotes in eclasses)
Date: Thu, 14 Feb 2008 16:52:57 +0300 [thread overview]
Message-ID: <1202997177.5803.36.camel@localhost> (raw)
In-Reply-To: <1202947821.826.1.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 2443 bytes --]
В Чтв, 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 #2: Эта часть сообщения подписана цифровой подписью --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-02-14 13:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-13 19:36 [gentoo-dev] missing quotes in eclasses Markus Meier
2008-02-13 19:42 ` Doug Klima
2008-02-13 20:28 ` Markus Meier
2008-02-13 20:49 ` Doug Klima
2008-02-14 0:10 ` Mart Raudsepp
2008-02-14 13:52 ` Peter Volkov [this message]
2008-02-14 14:03 ` [gentoo-dev] clean deprecated eclasses(?) Petteri Räty
2008-02-14 14:24 ` Rémi Cardona
2008-02-14 23:57 ` Chris Gianelloni
2008-02-14 16:41 ` [gentoo-dev] clean deprecated eclasses(?) (was: missing quotes in eclasses) Ciaran McCreesh
2008-02-14 23:25 ` Chris Gianelloni
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=1202997177.5803.36.camel@localhost \
--to=pva@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