extra-cmake-modules.git/tests/ECMSetupVersionTest, branch master hurd extra-cmake-modules.git Add another test for ECMSetupVersion 2021-08-06T06:43:29+00:00 Christophe Giboudeaux christophe@krop.fr 2021-08-06T06:43:29+00:00 fcd003b8b672f5a162e682b17a72ed2564be23a8 Amends: f0790f910 GIT_SILENT 
Amends: f0790f910
GIT_SILENT
ecm_setup_version: deal with 0-prefixed version values in PROJECT mode 2021-08-05T04:08:12+00:00 Friedrich W. H. Kossebau kossebau@kde.org 2021-08-05T04:08:12+00:00 a0f8e5469f388840d99aa8e8ff6f404cc16a66ad 5c191fa1d2383c69ddc075395e04f84b7679613a already added the same sanity check for the non-PROJECT mode 
5c191fa1d2383c69ddc075395e04f84b7679613a already added the same sanity
check for the non-PROJECT mode
Clean ECM files after the minimum version change 2021-05-25T08:07:34+00:00 Christophe Giboudeaux christophe@krop.fr 2021-05-17T09:44:44+00:00 c6e575539a4c0f370df65d15001e7f1b942b7e91 - Remove deprecated version checks - Use VERSION_GREATER_EQUAL 
- Remove deprecated version checks
- Use VERSION_GREATER_EQUAL
ECMSetupVersion: phase out deprecated *_VERSION_STRING CMake variables 2021-05-10T00:20:10+00:00 Friedrich W. H. Kossebau kossebau@kde.org 2021-05-03T15:58:02+00:00 9bf486f84ca333ccba65b5ffcb6f3e1bdcba3ecf 






Fix ECMSetupVersion tests for old policy with project() wo/ VERSION
2019-11-04T11:04:56+00:00

Friedrich W. H. Kossebau
kossebau@kde.org

2019-11-04T11:04:56+00:00

d2810741c2166354d7c95d4101eea52035d4fdf5

With min required cmake version now bumped to 3.5, the policy for CMP0048
needs to be set explicitly to old now to prepare what the tests check.

Fixup for 5ca01895e3c50322f79feeef5054d7f28b164d68





With min required cmake version now bumped to 3.5, the policy for CMP0048
needs to be set explicitly to old now to prepare what the tests check.

Fixup for 5ca01895e3c50322f79feeef5054d7f28b164d68







Raise CMake requirements to 3.5
2019-10-22T16:54:07+00:00

Hannah von Reth
vonreth@kde.org

2019-10-21T21:38:02+00:00

5ca01895e3c50322f79feeef5054d7f28b164d68












Revert "Add SameMajorVersionWithPreleases compat option to ecm_setup_version."
2015-01-24T14:47:59+00:00

Alex Merry
alex.merry@kde.org

2015-01-24T14:47:59+00:00

d609e598170064b4ee65392177a9d07f4302698d

This reverts commit 959c374c022394a116e8ceb2b1fce2df11752068.

I merged and pushed the wrong branch.





This reverts commit 959c374c022394a116e8ceb2b1fce2df11752068.

I merged and pushed the wrong branch.







Add SameMajorVersionWithPreleases compat option to ecm_setup_version.
2015-01-24T14:45:33+00:00

Alex Merry
alex.merry@kde.org

2014-12-28T15:03:07+00:00

959c374c022394a116e8ceb2b1fce2df11752068

SameMajorVersionWithPreleases is intended implement the versioning
scheme followed by many KDE projects: minor releases after some high
number (eg: 90) are considered to be pre-releases of the next major
version, and are not compatible with the current major version. This
allows alpha and beta releases to be ordered correctly by
version-number-aware software like package managers (an alpha of version
2 should have a higher number than any release of version 1, but less
than version 2.0).

So a request for version 2.1.0 of a piece of software should not be
satisfied by 2.93.4, because that is actually a pre-release of version
3. On the other hand, a request for version 2.91.0 should be satisfied
by version 3.1.0.

Note that prereleases are not considered unless explicitly requested, so
2.93.4 will not satisfy requests for version 3 (or version 2) of a piece
of software.





SameMajorVersionWithPreleases is intended implement the versioning
scheme followed by many KDE projects: minor releases after some high
number (eg: 90) are considered to be pre-releases of the next major
version, and are not compatible with the current major version. This
allows alpha and beta releases to be ordered correctly by
version-number-aware software like package managers (an alpha of version
2 should have a higher number than any release of version 1, but less
than version 2.0).

So a request for version 2.1.0 of a piece of software should not be
satisfied by 2.93.4, because that is actually a pre-release of version
3. On the other hand, a request for version 2.91.0 should be satisfied
by version 3.1.0.

Note that prereleases are not considered unless explicitly requested, so
2.93.4 will not satisfy requests for version 3 (or version 2) of a piece
of software.







Improve version file tests.
2014-12-28T17:30:11+00:00

Alex Merry
alex.merry@kde.org

2014-12-28T16:32:13+00:00

f8af407eba5c5ea45be2c6351cf41a7cb44fed21

Mostly just refatoring to have less duplicated code.





Mostly just refatoring to have less duplicated code.







Add COMPATIBILITY argument to ecm_setup_version().
2014-12-28T15:03:31+00:00

Alex Merry
alex.merry@kde.org

2014-12-27T15:28:39+00:00

bd69cdeea9aef1f254b7d83dd137a4de955151b7

Lots of libraries will want to use SameMajorVersion to make sure
searching for version 1 of a library doesn't give you version 2, for
example.

We may want to add another, custom compatibility mode for
KDE Frameworks-style versioning, where version x.90.z to x.99.z are
alpha/beta releases for version (x+1).

REVIEW: 121696





Lots of libraries will want to use SameMajorVersion to make sure
searching for version 1 of a library doesn't give you version 2, for
example.

We may want to add another, custom compatibility mode for
KDE Frameworks-style versioning, where version x.90.z to x.99.z are
alpha/beta releases for version (x+1).

REVIEW: 121696