Automatic calculation of package dependencies from CMake

[Neal Gompa]

On Sun, Aug 25, 2024 at 4:52 PM A. Wilcox <AWilcox at wilcox-tech.com> wrote:
>
> On Aug 25, 2024, at 2:58 PM, Ilya K <me at 0upti.me> wrote:
> >
> > Hey! We (NixOS) actually use repo-metadata for this, instead of parsing CMake files. This works decently well, and we just add non-KDE dependencies manually. I think the big problem with doing this cross-distro is having consistent names for packages everywhere. It might be a good idea to start with just pkg-config names and/or library sonames? At least those can be mostly figured out automatically with most tools.
>
> +1 for SONAMEs.  APK Tools can easily convert between them, so it’d be trivial to use for Adélie and any other system that uses APK.
>

For build-time dependencies, it's less easy to use sonames. But in the
RPM world, we can generate virtual identities for packages based on
all these things.

For example, "cmake(PlasmaWaylandProtocols)" is provided by
plasma-wayland-protocols-devel in Fedora, but also by
plasma-wayland-protocols in openSUSE. These standardized names have no
bearing on the actual package names because they are generated from
the information of the software itself.


-- 
真実はいつも一つ！/ Always, there's only one truth!