| 1 |
Stelian Ionescu wrote: |
| 2 |
> On Tue, 2009-09-29 at 16:32 +0300, Petteri Räty wrote: |
| 3 |
>> I wrote a script to check which ebuilds use built_with_use and have |
| 4 |
>> keywords in never versions making the ebuild unused. This means that |
| 5 |
>> neither arch or ~arch users are likely to install the ebuild. The script |
| 6 |
>> and the list of ebuilds is attached. I plan on removing all these |
| 7 |
>> ebuilds two weeks from now unless a reason is given why not to. If you |
| 8 |
>> see an ebuild on the list that should be kept, please migrate it to EAPI |
| 9 |
>> 2. If you need assistance in migrating, I can help. With these gone |
| 10 |
>> built_with_use usage will be down to about 600: |
| 11 |
> |
| 12 |
> built_with_use shouldn't be removed until EAPI=3 gets approved because |
| 13 |
> currently there's no good way to emulate "--missing true|false|die" |
| 14 |
> yes, I can use something like this in sbcl: |
| 15 |
> || ( <sys-libs/glibc-2.6[nptl] >=sys-libs/glibc-2.6 ) |
| 16 |
> but not all its use cases may be this simple |
| 17 |
> |
| 18 |
|
| 19 |
Even this is wrong because: |
| 20 |
|
| 21 |
betelgeuse@pena ~ $ portageq metadata / ebuild sys-libs/glibc-2.2.5-r10 IUSE |
| 22 |
nls |
| 23 |
|
| 24 |
For most packages old versions are not kept around so just doing |
| 25 |
>=cat/foo-X.Y[use] is fine and EAPI 3 is not needed. I haven't come |
| 26 |
across a case that couldn't be done with EAPI 2 yet. Granted the atoms |
| 27 |
can be a bit cleaner with EAPI 3 but considering how much zmedico slacks |
| 28 |
in implementing it, it's best to do migrating now with EAPI 2 than EAPI |
| 29 |
3 in the far future. |
| 30 |
|
| 31 |
Regards, |
| 32 |
Petteri |
Archives