Re: version numbers towards kf6
On Monday, 26 June 2023 17:32:18 CEST, Jos van den Oever wrote: On 26/06/2023 17.27, Heiko Becker wrote: On Monday, 26 June 2023 14:06:04 CEST, Jos van den Oever wrote: ... So that the user can see that they are running a snapshot and not an official release and to make it easy to report the correct version/snapshot in bug reports. Getting users to test and submit useful bug reports is the goal of these snapshot builds. I don't think it's possible to override PROJECT_VERSION, which for obvious reasons is an upstream choice and may influence other things like soversion. But I think you can use the qt6 keyword to tag bug reports.
Reminder: KF6 Meeting
Hello everyone, please remember the KF6 meeting tomorrow, Tuesday 17:00 CEST: https://meet.kde.org/b/ada-mi8-aem Topics and notes are collected here: https://invent.kde.org/teams/frameworks-devs/kf6-workboard/-/issues/45 Thank you, Volker signature.asc Description: This is a digitally signed message part.
Re: version numbers towards kf6
On 26/06/2023 17.27, Heiko Becker wrote: On Monday, 26 June 2023 14:06:04 CEST, Jos van den Oever wrote: On 26/06/2023 13.15, Heiko Becker wrote: On Monday, 26 June 2023 11:13:56 CEST, Jos van den Oever wrote: The new versions of frameworks, plasma and gear presumably all start with '6'. Following Fedora versioning for snapshots [0] gives this: 6^20230627git5328c27e3 Like Jonathan said, versioning of snapshots is a downstream thing. But if I understand the ^ operator correctly, doesn't sort 6^20230.. *after* 6.0? Indeed, it should be 6~20230627git5328c27e3 or 6.0.0~20230627git5328c27e3. And no, new versions of Gear won't start with '6'. They follow a different versioning scheme and some projects will probably switch to Qt6/KF6 with 22.12, some with 23.04 or later. I guess you mean 23.12 and 24.04. Time flies. Yeah, indeed. What is the best way to override the version numbers of KF6? cmake -DPROJECT_VERSION_MAJOR=6 ? Since there is no suffix support this would falsely indicate that it's already version 6 instead of a snapshot working towards it. Why do you want to override it it? So that the user can see that they are running a snapshot and not an official release and to make it easy to report the correct version/snapshot in bug reports. Getting users to test and submit useful bug reports is the goal of these snapshot builds. Best regards, Jos OpenPGP_signature Description: OpenPGP digital signature
Re: version numbers towards kf6
On Monday, 26 June 2023 14:06:04 CEST, Jos van den Oever wrote: On 26/06/2023 13.15, Heiko Becker wrote: On Monday, 26 June 2023 11:13:56 CEST, Jos van den Oever wrote: The new versions of frameworks, plasma and gear presumably all start with '6'. Following Fedora versioning for snapshots [0] gives this: 6^20230627git5328c27e3 Like Jonathan said, versioning of snapshots is a downstream thing. But if I understand the ^ operator correctly, doesn't sort 6^20230.. *after* 6.0? Indeed, it should be 6~20230627git5328c27e3 or 6.0.0~20230627git5328c27e3. And no, new versions of Gear won't start with '6'. They follow a different versioning scheme and some projects will probably switch to Qt6/KF6 with 22.12, some with 23.04 or later. I guess you mean 23.12 and 24.04. Time flies. Yeah, indeed. What is the best way to override the version numbers of KF6? cmake -DPROJECT_VERSION_MAJOR=6 ? Since there is no suffix support this would falsely indicate that it's already version 6 instead of a snapshot working towards it. Why do you want to override it it?
Re: version numbers towards kf6
On 26/06/2023 13.15, Heiko Becker wrote: On Monday, 26 June 2023 11:13:56 CEST, Jos van den Oever wrote: The new versions of frameworks, plasma and gear presumably all start with '6'. Following Fedora versioning for snapshots [0] gives this: 6^20230627git5328c27e3 Like Jonathan said, versioning of snapshots is a downstream thing. But if I understand the ^ operator correctly, doesn't sort 6^20230.. *after* 6.0? Indeed, it should be 6~20230627git5328c27e3 or 6.0.0~20230627git5328c27e3. And no, new versions of Gear won't start with '6'. They follow a different versioning scheme and some projects will probably switch to Qt6/KF6 with 22.12, some with 23.04 or later. I guess you mean 23.12 and 24.04. Time flies. Then for gear it makes sense to use $current^20230627git5328c27e3 e.g. 23.04^20230627git5328c27e3. What is the best way to override the version numbers of KF6? cmake -DPROJECT_VERSION_MAJOR=6 ? Since there is no suffix support this would falsely indicate that it's already version 6 instead of a snapshot working towards it. Best regards, Jos OpenPGP_signature Description: OpenPGP digital signature
Re: version numbers towards kf6
On Monday, 26 June 2023 11:13:56 CEST, Jos van den Oever wrote: The new versions of frameworks, plasma and gear presumably all start with '6'. Following Fedora versioning for snapshots [0] gives this: 6^20230627git5328c27e3 Like Jonathan said, versioning of snapshots is a downstream thing. But if I understand the ^ operator correctly, doesn't sort 6^20230.. *after* 6.0? And no, new versions of Gear won't start with '6'. They follow a different versioning scheme and some projects will probably switch to Qt6/KF6 with 22.12, some with 23.04 or later. Regards, Heiko
Re: version numbers towards kf6
The new versions of frameworks, plasma and gear presumably all start with '6'. Following Fedora versioning for snapshots [0] gives this: 6^20230627git5328c27e3 Having the commit date and the git revision in there helps with bug reports. But this disregards the context (build options, versions of other packages). The version number in CMakeLists.txt determines what users see in the about box and that is still e.g. set(PROJECT_VERSION "5.27.80") set(PROJECT_VERSION_MAJOR 5) CMake has no support for ^ or ~ with version suffixes [1]. Best regards, Jos [0] https://docs.fedoraproject.org/en-US/packaging-guidelines/Versioning/ [1] https://gitlab.kitware.com/cmake/cmake/-/issues/16716 On 26/06/2023 10.36, Jonathan Riddell wrote: Use whatever you like for your distro but for neon we have the not very elegant 5.92.0+p22.04+tunstable+git20230613.2104-0 for git master frameworks build frameworks version, ubuntu version, neon edition, date.time, buildnumber. Of course the frameworks version is meaningless there, it's just where I took the first packaging from, I'll update that once the frameworks get releases. Jonathan OpenPGP_signature Description: OpenPGP digital signature
Re: version numbers towards kf6
Use whatever you like for your distro but for neon we have the not very elegant 5.92.0+p22.04+tunstable+git20230613.2104-0 for git master frameworks build frameworks version, ubuntu version, neon edition, date.time, build number. Of course the frameworks version is meaningless there, it's just where I took the first packaging from, I'll update that once the frameworks get releases. Jonathan
version numbers towards kf6
Hello all, I'm packaging KF6 software in a nix flake [0]. I'm wondering what version numbers to use for packages built from the latest git commit from master. Best regards, Jos [0] https://invent.kde.org/vandenoever/kde-nix-flake/-/tree/kf6-qt6 OpenPGP_signature Description: OpenPGP digital signature
