On Fri Sep 26, 2003 at 05:57:52PM +0200, Buchan Milne wrote:

> >> It would be nice if packages would include an implicit epoch tag, so a
> >> package build on 9.2 will always be newer than one for 9.1 with the
> >> same version and release tags.
> >
> >
> > Hmmm, this is a neat idea.  At present, any mdk rpm you grab off the
> > net, you  have no idea what mandrake release it is built for.
> 
> At one stage, I had:
> %distribution         Mandrake Linux %distro_rel
> 
> (and a bit before it - which is still there since I use it in other
> macros - :
> %distro_rel             %(awk '{print $4}' /etc/mandrake-release)
> )
> 
> But rpmlint doesn't like this.
> 
> >
> > Would that work, having epoch: 9.2 in every package?  We use epoch so
> > rarely  that it might be okay, and we could use 9.2.1 if we REALLY
> > needed a new epoch,  right?
> >
> > Of course this would require a total rebuild of the distro, edited by
> > hand...  no small task.  Maybe this could be done at the same time that
> > we switch to a  full-distro rebuild robot that would force everyone to
> > fix their buildrequires  (me especially).
> 
> I don't know if automatic rebuilds can easily (and reliably) change
> version numbers or release numbers. Epoch numbers would have to be
> evaluated at build time, adding the packages own Epoch number, without
> having a recursive macro (which rpm doesn't like).
> 
> For the meantime, decrementing the release number by decimals may be a
> better idea.
> 
> BTW, I actually need a solution for this too. At present, all samba
> builds from the source release get identical %{version}-%{release} which
> is probably a bad thing ...

%define version 3.0
%define release 1
%define distro 92 

Version: %version
Release: %release.%distromdk

so you end up with 3.0-1.92mdk

umm.. untested.  =)  But you get the idea.

-- 
MandrakeSoft Security; http://www.mandrakesecure.net/
Online Security Resource Book; http://linsec.ca/
"lynx -source http://linsec.ca/vdanen.asc | gpg --import"
{FE6F2AFD : 88D8 0D23 8D4B 3407 5BD7  66F9 2043 D0E5 FE6F 2AFD}

Attachment: pgp00000.pgp
Description: PGP signature

Reply via email to