I've had a go at implementing CMake logic for the pre-release versioning that
KDE Frameworks use, where x.9y.z is a pre-release of (x+1).0.0 (eg: 4.90.0 is
the first prerelease of 5.0.0): https://git.reviewboard.kde.org/r/121719/
Frameworks don't have much use for this (we already named our CMake projects
with KF5 at the start), but I'm interested in knowing whether it would find use
in other projects - I don't want to commit code that no-one is going to use.
The usage would be that in ecm_setup_version() in your project, you would do
something like
ecm_setup_version(4.1.0
PACKAGE_VERSION_FILE MyProjectVersion.cmake
COMPATIBILITY SameMajorVersionWithPrereleases
FIRST_PRERELEASE_VERSION 90)
and then anyone searching for 3.91.0 would find this, but searches for 3.4.0
would not (on the basis that version 4 is incompatible with version 3).
If this would be useful for your project, please let me know.
Alex
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
