public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
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:34:10 +0300	[thread overview]
Message-ID: <4ACE5AD2.1020306@gentoo.org> (raw)
In-Reply-To: <1254916467.6236.11.camel@blackhole.cddr.org>

[-- Attachment #1: Type: text/plain, Size: 1473 bytes --]

Stelian Ionescu wrote:
> On Tue, 2009-09-29 at 16:32 +0300, 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:
> 
> built_with_use shouldn't be removed until EAPI=3 gets approved because
> currently there's no good way to emulate "--missing true|false|die"
> yes, I can use something like this in sbcl:
> || ( <sys-libs/glibc-2.6[nptl] >=sys-libs/glibc-2.6 )
> but not all its use cases may be this simple
> 

Even this is wrong because:

betelgeuse@pena ~ $ portageq metadata / ebuild sys-libs/glibc-2.2.5-r10 IUSE
nls

For most packages old versions are not kept around so just doing
>=cat/foo-X.Y[use] is fine and EAPI 3 is not needed. I haven't come
across a case that couldn't be done with EAPI 2 yet. Granted the atoms
can be a bit cleaner with EAPI 3 but considering how much zmedico slacks
in implementing it, it's best to do migrating now with EAPI 2 than EAPI
3 in the far future.

Regards,
Petteri


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  reply	other threads:[~2009-10-08 21:34 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
2009-10-07 11:54 ` Stelian Ionescu
2009-10-08 21:34   ` Petteri Räty [this message]
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=4ACE5AD2.1020306@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