Bernard Li wrote:
> Dear all:
>
> Currently if we are working on say version 3.9.0 and we want to build
> development version (i.e. from SVN/nightly), we would tag the SVN
> revision number and our names to the RPMs built, eg. 3.9.0r4002_bli.
>
> This causes an issue when the actual release comes about (3.9.0), you
> will not be able to upgrade via RPM since 3.9.0r4002_bli is > 3.9.0.
>
> Brian suggested that we do not increment the version until it is ready
> for release, eg. if we are working on 3.9.1 release, then we will
> build development releases as 3.9.0rXXXX until 3.9.1 is ready to be
> tagged.
>
> However, this will not work with 3.9.0, since we cannot go "back" as
> 3.8.x has a totally different meaning (even minor version is stable,
> odd minor version is unstable).
>
> Does anybody else have any comments/suggestions regarding this issue?
>
> I would like to avoid using RPM's epoch if at all possible...
What about using for example:
VERSION = 3.9.1-0_r4034_arighi
^^
Then, when 3.9.1 comes out rpm will automatically use 3.9.1-1 and it'll
be able to upgrade the 3.9.1-0_r4034_arighi.
-Andrea
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
sisuite-devel mailing list
sisuite-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-devel
