Re: Collection of packaging notes
On Fri, Nov 10, 2023 at 6:15 AM Christophe Marin wrote: > > Hello, > > On mercredi 1 novembre 2023 11:55:08 CET Christophe Marin wrote: > > Hello, > > > > With various alpha coming out soon, here are the notes added to my packages > > when I started packaging snapshots and still present. > > > > I now merged the frameworks and plasna packages in our openSUSE KDE repo to > see how the build behave. The frameworks builds went fine, but I can't say the > same about plasma. > > Some background: > For openSUSE, we want to give users the opportunity to choose when they want > to > migrate to plasma 6. The plasma packages won't be coinstallable, but they will > coexist for a while. > You're really asking for hard mode, aren't you? :) > From a packaging pov, we also make use of the CMake config name rather than > the corresponding -devel package when we need some build dependencies. > In most cases, the CMake config name will persist, even if the distro package > name > changes or upstream code moves to a different place. > > 3 different issues appeared with plasma 6 alpha: > > - The CMake config names are identical for certain core libraries: > KDecoration2, KPipeWire, KScreenLocker, KsysGuard, LayerShellQt, > LibKWorkspace, > LibTaskManager (and Breeze but it's slightly less problematic) > The versions emitted aren't the same, so you can use version ranges, e.g.: # kf5 version BuildRequires: (cmake(KPipeWire) >= 5.26 with cmake(KPipeWire) < 5.27.80) # kf6 version BuildRequires: cmake(KPipeWire) >= 5.27.80 > - The CMake config files for DBus interface are not versioned: > KRunnerAppDBusInterface, KWinDBusInterface, KSMServerDBusInterface, > ScreenSaverDBusInterface > This should not be a problem since the devel packages shouldn't be co-installable in any circumstance. > - The libksysguard libraries soversion weren't bumped. It's not only a > problem for > building plasma 5 and plasma 6. KSysguard is also an optional dependency > for kdevelop. > Well, okay, this is an issue. You'll also run into this with KUserFeedback. -- 真実はいつも一つ！/ Always, there's only one truth!
Re: Collection of packaging notes
Am Freitag, 10. November 2023, 12:36:09 CET schrieb Jonathan Riddell: > On Fri, 10 Nov 2023 at 10:55, Christophe Marin wrote: > > > - The libksysguard libraries soversion weren't bumped. It's not only a > > problem for > > building plasma 5 and plasma 6. KSysguard is also an optional dependency > > for kdevelop. > > I've bumped the soversions in libksysguard now. (I'll look at doing the > KFification for kuserfeedback too.) > > I've also release noted that ksysguard the app is dead and should be > removed from distros, it hasn't been released for over 2 years and hasn't > been ported. The Ksysguard dependency of kdevelop mentioned here is libksysguard which has a CMake name of ksysguard confusingly. > Jonathan David
Re: Collection of packaging notes
On Fri, 10 Nov 2023 at 10:55, Christophe Marin wrote: > 3 different issues appeared with plasma 6 alpha: > > - The CMake config names are identical for certain core libraries: > KDecoration2, KPipeWire, KScreenLocker, KsysGuard, LayerShellQt, > LibKWorkspace, > LibTaskManager (and Breeze but it's slightly less problematic) > > - The CMake config files for DBus interface are not versioned: > KRunnerAppDBusInterface, KWinDBusInterface, KSMServerDBusInterface, > ScreenSaverDBusInterface > As discussed on Matrix our assumption is that Plasma 5 and 6 aren't packaged together, a single version of Plasma should be packaged only with the same version. > - The libksysguard libraries soversion weren't bumped. It's not only a > problem for > building plasma 5 and plasma 6. KSysguard is also an optional dependency > for kdevelop. > I've bumped the soversions in libksysguard now. (I'll look at doing the KFification for kuserfeedback too.) I've also release noted that ksysguard the app is dead and should be removed from distros, it hasn't been released for over 2 years and hasn't been ported. Jonathan
Re: Collection of packaging notes
Hello, On mercredi 1 novembre 2023 11:55:08 CET Christophe Marin wrote: > Hello, > > With various alpha coming out soon, here are the notes added to my packages > when I started packaging snapshots and still present. > I now merged the frameworks and plasna packages in our openSUSE KDE repo to see how the build behave. The frameworks builds went fine, but I can't say the same about plasma. Some background: For openSUSE, we want to give users the opportunity to choose when they want to migrate to plasma 6. The plasma packages won't be coinstallable, but they will coexist for a while. >From a packaging pov, we also make use of the CMake config name rather than the corresponding -devel package when we need some build dependencies. In most cases, the CMake config name will persist, even if the distro package name changes or upstream code moves to a different place. 3 different issues appeared with plasma 6 alpha: - The CMake config names are identical for certain core libraries: KDecoration2, KPipeWire, KScreenLocker, KsysGuard, LayerShellQt, LibKWorkspace, LibTaskManager (and Breeze but it's slightly less problematic) - The CMake config files for DBus interface are not versioned: KRunnerAppDBusInterface, KWinDBusInterface, KSMServerDBusInterface, ScreenSaverDBusInterface - The libksysguard libraries soversion weren't bumped. It's not only a problem for building plasma 5 and plasma 6. KSysguard is also an optional dependency for kdevelop. Christophe
