List Archive: gentoo-dev
Note: Due to technical difficulties, the Archives are currently not up to date.
provides an alternative service for most mailing lists.c.f. bug 424647
On Thu, Oct 8, 2009 at 4:34 PM, Petteri Räty <firstname.lastname@example.org> wrote:
> 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
> 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
Comments like these are not acceptable. Zac works his tail off on
portage. Please refrain from such comments in the future.
> 3 in the far future.