On Sun, 9 Nov 2025 at 10:21, Aurélien COUDERC <[email protected]> wrote:
> Hi > > I have a WIP solution, that I *may* land for 6.6, if you're interested in > the implementation you can have a look at : > - <https://salsa.debian.org/qt-kde-team/kde/plasma-version#> > - < > https://salsa.debian.org/qt-kde-team/pkg-kde-tools/-/commit/fa730bf00427579d953b79cd95a1a2c5fe0a8f95 > > > - < > https://salsa.debian.org/qt-kde-team/kde/breeze-grub/-/commit/4501b5cb0e4e7501693cd977410e9cf7d4963712 > > > > > Happy hacking, > -- > Aurélien > > Hi, Wouldn't this force a rebuild of all the packages that depend on the plasma-version-base-${plasma-version:major}.${plasma-version:minor} every time when the version changes? Could this same or at least similar result be reached with stricter dependencies in the packages? Example: currently plasma-workspace has dependency kwin-wayland (>= 4:6.2.90~). What if this and all the similar dependencies are updated to something like kwin-wayland (>= 4:${plasma-version:major}.${plasma-version:minor}~). Wouldn't that prevent installing plasma-workspace in testing before kwin-wayland has also migrated? -- Sami Erjomaa
