perfsonar-dev - Re: [pS-dev] Re: perfSONAR MDM 3.1 update status
Subject: perfsonar development work
List archive
- From: Antoine Delvaux <>
- To:
- Subject: Re: [pS-dev] Re: perfSONAR MDM 3.1 update status
- Date: Thu, 05 Mar 2009 14:30:00 +0000
- Organization: eShango
I added those notes to the package creation wiki pages at
http://wiki.perfsonar.net/jra1-wiki/index.php/Packaging/Creating_DEB_Package_files
and
http://wiki.perfsonar.net/jra1-wiki/index.php/Packaging/Creating_RPM_Package_files
Let me know if anything remains unclear.
Thanks,
Antoine.
Szymon Trocha a écrit :
> Antoine Delvaux pisze:
>>>> I don't know if we can do something at packages level. I'd like to have
>>>> developers opinion here?
>>>>
>>> I'm sure there is a mechanism at packages level to properly indicate
>>> beta versions.
>>
>> Yes, there is.
>>
>> The RPM way is to use the 'Release' field of the SPEC file and have
>> something
>> begining with '0.' in it. When the final package is done, this is
>> bumped to
>> '1', and so any RC package will be upgraded.
>>
>> In the SPEC file you'll have (for the first RC):
>> Version: 2.1
>> Release: 0.rc1.1
>>
>> Second RC:
>> Version: 2.1
>> Release: 0.rc2.1
>>
>>
>> and for the final:
>> Version: 2.1
>> Release: 1.0
>>
>> The Deb way, lacking a 'release' field, is to decrease the version
>> number for RC
>> and adding '+1' at the end.
>>
>> In the debian/changelog file, you'll have (for the first RC):
>> package-name (2.0.99+1.rc1-1)
>>
>> Second RC:
>> package-name (2.0.99+1.rc2-1)
>>
>> and for the final:
>> package-name (2.1-1)
>
> Thank you Antoine. This is something to consider for next MDM releases
> then.
>
> Regards,
--
Antoine Delvaux Systems Engineer
DANTE Tel: +44.1223371300
http://www.dante.net Fax: +44.1223371371
PGP fingerprint: DC65 0D8B 6938 9229 33C3 18CA 4EB6 09D3 A333 3378
- Re: [pS-dev] Re: perfSONAR MDM 3.1 update status, Antoine Delvaux, 03/05/2009
Archive powered by MHonArc 2.6.16.