Re: Marble versioning
Johannes Zarl-Zierl <[email protected]> Wed, 28 Jul 2021 23:47:38 +0200
| Newsgroups | gmane.comp.kde.kimdaba |
|---|---|
| Message-ID | <37850902.MHN8ft9vk3@jo2021> |
--===============1293914938000153303== Content-Type: multipart/signed; boundary="nextPart2146139.7brS7yEKiq"; micalg="pgp-sha512"; protocol="application/pgp-signature" --nextPart2146139.7brS7yEKiq Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii"; protected-headers="v1" From: Johannes Zarl-Zierl <[email protected]> To: [email protected] Subject: Re: [KPhotoAlbum] Marble versioning Date: Wed, 28 Jul 2021 23:47:38 +0200 Message-ID: <37850902.MHN8ft9vk3@jo2021> In-Reply-To: <1863231.fIoEIV5pvu@ginuog> References: <2090122.C4sosBPzcN@ginuog> <542476406.ZSs0jgxMRr@jo2021> <1863231.fIoEIV5pvu@ginuog> Am Mittwoch, 28. Juli 2021, 07:35:15 CEST schrieb Tobias Leupold: > > Semantic versioning is clearly a better approach if done correctly. If not > > done correctly (or at all), automatic YYYY.mm versioning is at least > > reliable and allows us to write checks. > > Hey, it's not worse than KDE frameworks ;-) > > But how do we reliably address the problem that the "major" version > increases, also if no API changes have been done? You mean from a build-system perspective or from the perspective of an API user? The build-system part will be solved with time (the next release of marble should have the version compatibility set to "AnyNewerVersion"). Until then, the cmake snippet posted before should be a suitable workaround: find_package(Marble) if((${Marble_VERSION} VERSION_LESS 0.28) # instead of bailing out with a message use a find_package call so that messages are the same as normally, and so that feature_summary works correctly: find_package(Marble 0.28 REQUIRED) endif() Once we can rely on the next release (say, 21.09), "find_package(Marble 21.09 REQUIRED)" will work for the future and also match 22.04 etc. Cheers, Johannes --nextPart2146139.7brS7yEKiq Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEl6nGIhrxKR+gDIJesUNk9Y9clpgFAmEB0HoACgkQsUNk9Y9c lpgbEgf+I4okNc5NqLmEWRI+sp9BUidj8EHzGRMdn5EYBuWj6NKwg+2eQ13hwOLx /g6pI4K05/IlVP6vQlG0uy7FULzi4MZwPqsqyQ9x/eU3WyI010Ho4oDQ2Pl/lr2v ZOnV5gBrkUyaBZsvkdZh8vlJs86PkRUCq513kkNg+pqYNQhM44BFGN6+64QUanGs TW8LzoZToGp9aWXQPObFDbTYJejt/vhpEU/JcRJfHbirj03dD1XWIMABr1N/9Qgh 9Qk5mOr863K1PekMGjemUKJKbmtCzB7sJD7oTUOhe3Lb8PCiG0PGfbccyFGJGyZH Y6v76UI4sRUyctYr8TRoefaxvdUUQg== =1gKN -----END PGP SIGNATURE----- --nextPart2146139.7brS7yEKiq-- --===============1293914938000153303== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ KPhotoAlbum mailing list [email protected] https://mail.kdab.com/mailman/listinfo/kphotoalbum --===============1293914938000153303==--