Details
-
Suggestion
-
Resolution: Unresolved
-
P3: Somewhat important
-
None
-
None
-
None
Description
QtWebEngine should be decoupled form qt releases , introducing another versioning schema which follows chromium one (like QtWebEnigne.so.98.1) makes more sense and makes easy to understand releases . Currently we plan release of 6.2 with web engine 6.3 which claims has of version 6.2..... why oh why ? Fix numbering schema is required to decouple qtwebenigne for qt releases on linux platform as compiling source from other version and overloading version number is not a sane solution.
Making changes requires cmake to make EXPORT files in more generic manner able to set numbering schema independent for each module.
Attachments
Issue Links
- relates to
-
QTBUG-96458 Make it possible to build newer Qt modules against older Qt
- Closed
Gerrit Reviews
For Gerrit Dashboard: QTBUG-103500 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
411536,13 | CMake: Add new version numbering schema | dev | qt/qtwebengine | Status: NEW | +1 | 0 |
419921,11 | CMake: Add support for overriding Qt6ConfigVersion.cmake | dev | qt/qtbase | Status: NEW | +2 | 0 |
420313,4 | CMake: Fix usage of QT_NO_PACKAGE_VERSION_CHECK | dev | qt/qtbase | Status: NEW | +2 | 0 |
411548,3 | Use dependecy versioning based on qt core version | 6.3 | qt/qtbase | Status: ABANDONED | 0 | 0 |
418680,21 | CMake: Record used package version for each target dependency | dev | qt/qtbase | Status: MERGED | +2 | 0 |
418936,2 | WIP: CMake: Test mixing of Qt package versions | dev | qt/qtsvg | Status: ABANDONED | -2 | 0 |
422762,2 | CMake: Record used package version for each target dependency | 6.4 | qt/qtbase | Status: MERGED | +2 | 0 |