RPM Community Forums

Mailing List Message of <rpm-devel>

Re: new DISTEPOCH tag and cleaning of RELEASE tag polution

From: Per ěyvind Karlsen <pkarlsen@rpm5.org>
Date: Mon 22 Dec 2008 - 17:14:59 CET
Message-ID: <534660c60812220814x2e54394eycc6a05167acc4548@mail.gmail.com>
2008/12/22 Per ěyvind Karlsen <pkarlsen@rpm5.org>

> 2008/12/21 Arkadiusz Miskiewicz <arekm@pld-linux.org>
>
>> On Saturday 20 of December 2008, Per ěyvind Karlsen wrote:
>> > I've modified DISTTAG tag to be specified in macros file just like
>> > DISTRIBUTION, VENDOR etc.
>> > and commited it to CVS already.
>> > Here's my next step, a DISTEPOCH tag where distribution version can be
>> > added.
>> >
>> > This will change EVR to EVRD which will be represented as
>> > %{EPOCH}:%{VERSION}-%{RELEASE}:%{DISTEPOCH}, ie. 1:2.3.4-5:2009.1.
>>
>> In PLD this won't fly because
>> 1:2.3.4-5 in "new" devel version of distro can be newer than
>> 1:2.3.4-7 in "old" still maintained one.
>>
>> (versioning is separate for each line)
>>
>> For now in such case -5 would be bumped to something bigger than in "old"
>> version manually.
>
> So does this mean that for PLD such a DISTEPOCH tag would be the most
> significant value rather than least significant?
>
> Would 1:2.3.4-7 then be a different release other than which distro release
> it's
> built for?
> In Mandriva the packages with the same release are always built from the
> same
> package between releases, updates etc. of a package in a stable
> distribution
> is rather given a release like 1:2.3.4-5.1 rather than 1:2.3.4-6..
>

btw. here's some info on release tags in Mandriva Linux:
http://wiki.mandriva.com/en/Policies/Release_Tag
Received on Mon Dec 22 17:15:01 2008
Driven by Jeff Johnson and the RPM project team.
Hosted by OpenPKG and Ralf S. Engelschall.
Powered by FreeBSD and OpenPKG.