https://bugs.kde.org/show_bug.cgi?id=402428
--- Comment #4 from Nate Graham <n...@kde.org> --- After attempting to actually use our developer documentation that recommends kdesrc-build while pretending to not know anything that I know, the issue of fetching non-KDE dependencies kept coming up again and again. kdesrc-build works fantastically well as long as you have all the non-KDE dependencies installed. If you don't, it's an exercise in extreme frustration reading log files one by one trying to parse CMake errors and map them to package names that you then go out and manually install. I think it must be a minor miracle when a new contributor has the patience to work through this. I would be happy to contribute to fixing this bug by compiling the mapping of KDE-project-to-distro-package-name, and I can help with the code too since I know Perl. Conceptually I think we need a mapping that allows for each piece of software to have one or more distro packages associated with it. For example, KIO: frameworks/kio ############## Arch: kio KDE Neon: kio Ubuntu: libkf5kiocore5 libkf5kiofilewidgets5 libkf5kiogui5 libkf5kiontlm5 libkf5kiowidgets5 frameworks/kconfigwidgets Arch: kconfigwidgets KDE Neon: kconfigwidgets Ubuntu: libkf5configwidgets5 [etc] So when you do `kdesrc-build-kio --include-dependencies` it would go out and fetch the dependencies for kio and all of its KDE dependencies using the distro's package manager, e.g. sudo apt build-dep kio kconfigwidgets [etc] We might also need a way of adding specificity regarding the major version of the KDE software, plus a way to have the package names change over time with different distro version releases. -- You are receiving this mail because: You are watching all bug changes.
