From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Old eclasses - candidates for removal?
Date: Thu, 4 Jun 2009 23:05:57 +0200 [thread overview]
Message-ID: <18984.14133.179507.71357@a1ihome1.kph.uni-mainz.de> (raw)
In last week's council meeting a policy for removal of old eclasses
has been defined:
,----
| The council voted that to remove eclasses devs should take the
| following steps:
| 1) Deprecate eclasses.
| 2) Removal of all functionality relating to installing.
| 3) After two years the eclass may be removed.
`----
A quick scan shows that the following eclasses were deprecated more
than three years ago, and are used by no ebuild in the tree:
2002-05-25 inherit.eclass
2003-12-11 kde-i18n.eclass
2004-04-16 koffice-i18n.eclass
2005-09-18 jakarta-commons.eclass
2006-02-28 php.eclass
2006-02-28 php-2.eclass
Do we want to remove any of these? Have I missed other candidates?
Ulrich
next reply other threads:[~2009-06-04 21:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-04 21:05 Ulrich Mueller [this message]
2009-06-04 21:11 ` [gentoo-dev] Old eclasses - candidates for removal? Tomáš Chvátal
2009-06-04 21:14 ` Krzysiek Pawlik
2009-06-04 21:35 ` Theo Chatzimichos
2009-06-04 22:42 ` Petteri Räty
2009-06-06 4:52 ` Jorge Manuel B. S. Vicetto
2009-06-07 13:44 ` Petteri Räty
2009-06-05 6:52 ` Tobias Klausmann
2009-06-05 9:46 ` Ulrich Mueller
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=18984.14133.179507.71357@a1ihome1.kph.uni-mainz.de \
--to=ulm@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