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

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

[Jodok Batlogg]

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.

thanks in advance

jodok

--------------------------------------------------------------------------
# Copyright 2003 Gentoo Technologies, Inc.
# Distributed under the terms of the GNU General Public Form License v2
# $Header: /home/cvs/gentoo/portage/net-zope/plone/plone-1.0.4-r1.ebuild,v
1.1 2003/08/05 19:45:48 jb Exp $

SLOT="1.0"

inherit zproduct
S="${WORKDIR}/CMFPlone-${PV}"

DESCRIPTION="A Zope Content Management System, based on Zope CMF."
HOMEPAGE="http://plone.org"
SRC_URI="mirror://sourceforge/plone/CMFPlone${PV}.tar.gz"
LICENSE="GPL-2"
KEYWORDS="x86 ~ppc"
RDEPEND="=net-zope/cmf-1.3*
        >=net-zope/dcworkflow-1.0.4
        >=net-zope/formulator-1.2.0
        ${RDEPEND}"

ZPROD_LIST="CMFPlone"

src_install()
{
        rm -R Formulator/
        rm -R DCWorkflow/
        zproduct_src_install all
}

# Since i18n isn't a product folder, leaving it in $ZP_DIR/$PF.

pkg_postinst()
{
        zproduct_pkg_postinst
        einfo "---> NOTE: i18n folder location: ${ZP_DIR}/${PF}"
}


--------------------------------------------------------------------------
# Copyright 2003 Gentoo Technologies, Inc.
# Distributed under the terms of the GNU General Public Form License v2
# $Header:
/home/cvs/gentoo/portage/net-zope/plone/plone-1.1_pre20030805.ebuild,v 1.2
2003/08/05 21:40:40 jb Exp $

SLOT="1.1"

inherit zproduct
S="${WORKDIR}/CMFPlone-1.1"

DESCRIPTION="A Zope Content Management System, based on Zope CMF."
HOMEPAGE="http://plone.org"
SRC_URI="http://gentoo.at/distfiles/CMFPlone${PV}.tar.gz"
LICENSE="GPL-2"
KEYWORDS="~x86 ~ppc"
RDEPEND="=net-zope/cmf-1.4*
    =net-zope/dcworkflow-1.4*
    >=net-zope/formulator-1.4.2
    >=net-zope/cmfactionicons-0.1_pre20030805
    >=net-zope/cmfquickinstallertool-1.2.1
    >=net-zope/groupuserfolder-1.3.1
        >=net-zope/externaleditor-0.7
        >=net-zope/btreefolder2-0.5.0
    ${RDEPEND}"

ZPROD_LIST="CMFPlone"

--------------------------------------------------------------------------

jodok batlogg
solution2u.net gmbh . hof 4 . a-6861 alberschwende
fon +43 5579 85777-65 . fax -77 . mobil +43 699 11841546
http://solution2u.net/ . batlogg(at)solution2u(dot)net

have a nice day


--
gentoo-dev@gentoo.org mailing list

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

[Martin Schlemmer]

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

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


Regards,

-- 

Martin Schlemmer
Gentoo Linux Developer, Desktop/System Team Developer
Cape Town, South Africa



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

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

[Martin Schlemmer]

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

On Mon, 2003-08-11 at 03:10, 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
> 

BTW:  why was it never SLOTted ?


-- 

Martin Schlemmer
Gentoo Linux Developer, Desktop/System Team Developer
Cape Town, South Africa



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

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

[Jodok Batlogg]

Martin Schlemmer wrote:

> On Mon, 2003-08-11 at 03:10, 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
>> 
> 
> BTW:  why was it never SLOTted ?
> 
> 
Martin Schlemmer wrote:

> On Mon, 2003-08-11 at 03:10, 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
>> 
> 
> BTW:  why was it never SLOTted ?
> 
> 

i think nobody thought it will be needed ;-) 
but as the plone project grows... we're at the point slots are useful.

regards

jodok
-- 
jodok batlogg
solution2u.net gmbh . hof 4 . a-6861 alberschwende
fon +43 5579 85777-65 . fax -77 . mobil +43 699 11841546
http://solution2u.net/ . batlogg(at)solution2u(dot)net

have a nice day 


--
gentoo-dev@gentoo.org mailing list

[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@gentoo.org mailing list

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

[Martin Schlemmer]

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

On Mon, 2003-08-11 at 08:32, Jodok Batlogg wrote:

> > 
> > BTW:  why was it never SLOTted ?
> > 
> > 
> 
> i think nobody thought it will be needed ;-) 
> but as the plone project grows... we're at the point slots are useful.
> 

No excuse, if no SLOT, it should be set to "0".


-- 

Martin Schlemmer
Gentoo Linux Developer, Desktop/System Team Developer
Cape Town, South Africa



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

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

[Martin Schlemmer]

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

On Mon, 2003-08-11 at 08:36, Jodok Batlogg wrote:
> 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?
> 

Nope.  Maybe try an unstable/older version ?  Or place them
directly in the tree.


-- 

Martin Schlemmer
Gentoo Linux Developer, Desktop/System Team Developer
Cape Town, South Africa



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]