[Kde-extra-gear] Evaluation of the extragear tarball releases.

[Angelo Naselli]

> Okido. Well let's take a made up applicatin as an example. 
> 
> The release-team releasese kdrip-3.97.tgz which happens to have as version number '1.3'. Up to now the distro's have added the kdrip in their archives as kdrip-1.2 (latest official release). With this new 
release they have a choice. add it as 3.97 or as 1.3. Either one is a problem:
> 1.3: when the official release of 1.3 happens. they can not name it like that because it is already used ny the release-team release
> 3.97: when the official release of 1.3 happens, they can not name it like that because 3.97 > 1.3
I'm not familiar with cmake yet, but since something like that could have been done into 
autotools it should be here as well, i believe. Something like  
SET(KDRIP_VERSION "1.3") into the higher cmakelist.txt and managed by the project?
In such a way you can have the big tarball with keg release version, but it should contains right
project versions.
That could be a problem anyway becuase if they eventually release the official one 1.3 is newer but 
with the same version, a pre version should be agreed with project developers anyway i believe.

My 2€cents,
	Angelo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-extra-gear/attachments/20080114/adce8347/attachment.pgp