From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Unused ebuild built_with_use cleanup
Date: Fri, 09 Oct 2009 00:29:08 +0300 [thread overview]
Message-ID: <4ACE59A4.8090501@gentoo.org> (raw)
In-Reply-To: <4ACC79D1.5070405@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1858 bytes --]
Marijn Schouten (hkBst) wrote:
> Petteri Räty wrote:
>> I wrote a script to check which ebuilds use built_with_use and have
>> keywords in never versions making the ebuild unused. This means that
>> neither arch or ~arch users are likely to install the ebuild. The script
>> and the list of ebuilds is attached. I plan on removing all these
>> ebuilds two weeks from now unless a reason is given why not to. If you
>> see an ebuild on the list that should be kept, please migrate it to EAPI
>> 2. If you need assistance in migrating, I can help. With these gone
>> built_with_use usage will be down to about 600:
>
> I have some ebuilds on the list: plt-scheme, stklos, lilypond. I usually clean
> up unused ebuilds some time after a new version has gone stable.
>
> Anyway my question is: what is the point of removing unused versions in the
> proposed manner? If the newer version is not ported to EAPI 2 and also uses
> built_with_use what do we gain? Even if it is already ported, do we gain
> anything by the propsed removal? Are all unused ebuilds evil?
>
It saves my time when removing built_with_use from packages that still
have active versions using it. Many packages are also unmaintained so
the versions with built_with_use don't get removed without doing
something like this.
> If built_with_use is to be eliminated from the tree I propose that effort is
> directed towards porting and stabling ebuilds that still use it. After the
> stable version has begun using EAPI 2 use deps, then all uses of built_with_use
> in other versions can be considered obsolete and those ebuilds can be removed in
> one fell sweep if need be.
>
It will be eliminated eventually. I am in the process of doing so but as
you can see from the numbers it takes quite a lot of work to get rid of
them.
Regards,
Petteri
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2009-10-08 21:29 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 13:32 [gentoo-dev] Unused ebuild built_with_use cleanup Petteri Räty
2009-10-07 11:21 ` Marijn Schouten (hkBst)
2009-10-08 21:29 ` Petteri Räty [this message]
2009-10-07 11:54 ` Stelian Ionescu
2009-10-08 21:34 ` Petteri Räty
2009-10-08 22:03 ` Jeremy Olexa
2009-10-08 22:22 ` Petteri Räty
2009-10-09 0:17 ` Patrick Lauer
2009-10-09 13:38 ` Petteri Räty
2009-10-08 22:25 ` Tomáš Chvátal
2009-10-09 13:41 ` Petteri Räty
2009-10-24 12:32 ` [gentoo-dev] Re: [gentoo-dev-announce] " Petteri Räty
2009-10-24 20:29 ` James Cloos
2009-10-25 9:48 ` Petteri Räty
2009-10-26 23:21 ` James Cloos
2009-10-27 13:12 ` Petteri Räty
2009-10-27 6:07 ` Ryan Hill
2009-10-27 7:02 ` Mike Frysinger
2009-10-27 13:09 ` Petteri Räty
2009-10-27 13:46 ` Mike Frysinger
2009-10-27 18:46 ` Petteri Räty
2009-10-28 2:31 ` [gentoo-dev] " Mike Frysinger
2009-10-28 9:51 ` Petteri Räty
2009-10-28 11:11 ` Alexis Ballier
2009-10-30 2:29 ` Doug Goldstein
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=4ACE59A4.8090501@gentoo.org \
--to=betelgeuse@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