kdelibs 4.8? What to do about GENERIC_LIB_VERSION?

todd rme toddrme2178 at gmail.com
Mon Oct 3 15:14:05 BST 2011


On Mon, Oct 3, 2011 at 2:45 PM, Allen Winter <winter at kde.org> wrote:
> On Monday 03 October 2011 5:04:45 AM Albert Astals Cid wrote:
>> A Dilluns, 3 d'octubre de 2011, Alexander Neundorf vàreu escriure:
>> > On Monday 03 October 2011, Allen Winter wrote:
>> > > Howdy,
>> > >
>> > > A lot of CMakeLists.txt use the ${GENERIC_LIB_VERSION} to set the so
>> > > versioning of their libraries. That variable is hard-coded in
>> > > kdelibs/cmake/modules/KDE4Defaults.cmake
>> > >
>> > > If we rely on kdelibs-4.7 for the KDE SC 4.8 release, then all the
>> > > shared
>> > > libraries using ${GENERIC_LIB_VERSION} will be still set to 4.7.  for
>> > > example the kdepimlbs kcalcore library will be versioned to 4.7.0
>> > > instead
>> > > of 4.8.0 in the KDE SC 4.8 release.
>> >
>> > How about simply increasing the version number to 4.8 ?
>> > This would also give the libs in kdelibs the version number 4.8, but I don't
>> > see a problem with that.
>>
>> Third time in this thread. This is Dirk's plan all along.
>>
> Ok then.
> If there are no objections I will increase the variables in kdelibs-4.7 to say "4.8"

Shouldn't this track the pre-release numbering once we have some
pre-releases (like 4.7.85 or something)?

-Todd




More information about the kde-core-devel mailing list