[gentoo-dev] Re: custom ebuild: AUTOCLEAN unmerges slotted version

[Jodok Batlogg]

Martin Schlemmer wrote:

> On Mon, 2003-08-11 at 00:55, Jodok Batlogg wrote:
>> hi,
>>
>> i'm preparing an ebuild for plone1.1 (zope based CMS). I took the
>> existing 1.04-ebuild and added SLOT="1.0" and SLOT="1.1".
>>
>> the ebuilds work fine, but although i specified two different slots
>> AUTOCLEAN always unmerges the lower version. I have no idea why.
>>
>> i've attached the two ebuilds. is there sth. obvious i'm missing? i can't
>> find the reason.
>>
>
> You need to remerge the old version with the updated SLOT first.
> This will tipically be one of those things that update goes as
> follows:
>
> 1) add new revision of older version with new SLOT
> 2) wait a few weeks (days?) for it to propagate
> 3) add the new version with diff SLOT

yes, i know this is normal procedure. what i wanted to do: test it locally.
i "simulated" the above behaviour already:

- unmerge entire package (in all versions)
- set PORTAGE_OVERLAY (all my new ebuilds are there)
- deleted the "normal" ebuilds in /usr/portage (i know this is usually not
necessary)
- regenworld
- emerge the one with slot 1.0
- emerge the one with slot 1.1

is there a "global" switch which packages are slotted?

thanks

jodok


--
gentoo-dev@g.o mailing list