https://bugs.kde.org/show_bug.cgi?id=402428
--- Comment #5 from Michael Pyne <mp...@kde.org> --- Part of this is already starting, though it's focused on getting kdesrc-build and critical dependencies installed common to most of KDE software (e.g. cmake, gcc, X11 or Wayland but not necessarily packages specific only to Krita or KDevelop). See modules/ksb/OSSupport.pm (to figure out which distro we're on) and modules/ksb/FirstRun.pm (to encode which distro releases go to which packages to install). In particular OSSupport.pm already tries to provide a concept of distro versions, we could add metadata there to return the proper per-distro packager cmdline invocation. OSSupport.pm uses the systemd os-release standard which allows scripts to interrogate to increasingly more-generic versions of distros (e.g. Neon -> Ubuntu -> Debian or Manjaro -> Arch) so we hopefully would only need to support a few. For per-app dependencies we could use the existing kde-build-metadata repository to hold the data mapping (rather than putting it in kdesrc-build itself). Would need to be JSON or YAML (we already have to support both). YAML is probably easier since you can provide comments :P Conceptually we could then have a pseudo-module be added to the build list before the user's module list (but after kde-build-metadata), with a special Updater/BuildSystem setup to use the distro's own package manager to install dependencies for all modules in the build list. I'm absolutely willing to push this feature forward but I could use help. :) Remember we're trialing Gitlab-based workflow for kdesrc-build on https://invent.kde.org/ so if you haven't already hopped over I'd love to get you integrated into some issues/merge requests. -- You are receiving this mail because: You are watching all bug changes.
