| 1 |
On Mon, 2003-08-11 at 08:36, Jodok Batlogg wrote: |
| 2 |
> Martin Schlemmer wrote: |
| 3 |
> |
| 4 |
> > On Mon, 2003-08-11 at 00:55, Jodok Batlogg wrote: |
| 5 |
> >> hi, |
| 6 |
> >> |
| 7 |
> >> i'm preparing an ebuild for plone1.1 (zope based CMS). I took the |
| 8 |
> >> existing 1.04-ebuild and added SLOT="1.0" and SLOT="1.1". |
| 9 |
> >> |
| 10 |
> >> the ebuilds work fine, but although i specified two different slots |
| 11 |
> >> AUTOCLEAN always unmerges the lower version. I have no idea why. |
| 12 |
> >> |
| 13 |
> >> i've attached the two ebuilds. is there sth. obvious i'm missing? i can't |
| 14 |
> >> find the reason. |
| 15 |
> >> |
| 16 |
> > |
| 17 |
> > You need to remerge the old version with the updated SLOT first. |
| 18 |
> > This will tipically be one of those things that update goes as |
| 19 |
> > follows: |
| 20 |
> > |
| 21 |
> > 1) add new revision of older version with new SLOT |
| 22 |
> > 2) wait a few weeks (days?) for it to propagate |
| 23 |
> > 3) add the new version with diff SLOT |
| 24 |
> |
| 25 |
> yes, i know this is normal procedure. what i wanted to do: test it locally. |
| 26 |
> i "simulated" the above behaviour already: |
| 27 |
> |
| 28 |
> - unmerge entire package (in all versions) |
| 29 |
> - set PORTAGE_OVERLAY (all my new ebuilds are there) |
| 30 |
> - deleted the "normal" ebuilds in /usr/portage (i know this is usually not |
| 31 |
> necessary) |
| 32 |
> - regenworld |
| 33 |
> - emerge the one with slot 1.0 |
| 34 |
> - emerge the one with slot 1.1 |
| 35 |
> |
| 36 |
> is there a "global" switch which packages are slotted? |
| 37 |
> |
| 38 |
|
| 39 |
Nope. Maybe try an unstable/older version ? Or place them |
| 40 |
directly in the tree. |
| 41 |
|
| 42 |
|
| 43 |
-- |
| 44 |
|
| 45 |
Martin Schlemmer |
| 46 |
Gentoo Linux Developer, Desktop/System Team Developer |
| 47 |
Cape Town, South Africa |
Archives