[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-extra-gear
Subject:    Re: [Kde-extra-gear] Evaluation of the extragear tarball releases.
From:       Angelo Naselli <anaselli () linux ! it>
Date:       2008-01-14 10:06:12
Message-ID: 200801141106.12594.anaselli () linux ! it
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


> 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


["signature.asc" (application/pgp-signature)]

_______________________________________________
Kde-extra-gear mailing list
Kde-extra-gear@kde.org
https://mail.kde.org/mailman/listinfo/kde-extra-gear


[prev in list] [next in list] [prev in thread] [next in thread]