[packagers] Who to package programs with alphanumerical versions?

[Heiko Adams]

Am Dienstag, den 25.03.2008, 16:19 +0100 schrieb Dag Wieers:
> On Tue, 25 Mar 2008, Heiko Adams wrote:
> 
> > can anyone give me a hint how to create packages and specfiles for
> > alphanumerical versions like 0.2.12b??
> > This problem drives me crazy.
> 
> Sometimes the 'b' indicates a second release, in that case you can leave 
> the b in the version string (see the cacti release strings).
> 
> But if the 'b' means 'beta', then it means the real 0.2.12 version is 
> yet to be releases and we have to be careful because 0.2.12b > 0.2.12.
> In that case, you have to do:
> 
>  	%define real_version 0.2.12b
>  	Version: 0.2.12
>  	Release: 0.b
> 
> and the next package becomes:
> 
>  	%define real_version 0.2.12b
>  	Version: 0.2.12
>  	Release: 0.1.b
> 
> until 0.2.12 is released, which then becomes:
> 
>  	Version: 0.2.12
>  	Release: 1
> 
> Kind regards,
Thanks, but how do I tell rpmbuild to use the directory
<program>_0.2.12b instead of <program>_0.2.12b for configure and make?

Regards
-- 
Heiko Adams <heiko.adams at gmail.com>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : http://lists.rpmforge.net/pipermail/packagers/attachments/20080325/c2f532a5/attachment.bin