For reference from the meeting as something to build off of:

https://pagure.io/fedora-comps/blob/main/f/comps-f41.xml.in#_3206
https://pagure.io/fedora-comps/blob/main/f/comps-f41.xml.in#_3166
https://pagure.io/fedora-comps/blob/main/f/comps-f40.xml.in#_3455

See also the list in https://github.com/travier/quay-containerfiles/blob/main/toolbox-kdedev/Containerfile#L47, which is a toolbox container that I use to do KDE development.

I think this is where kf6-software-development comps group would help.

While kf6 is part of the dependencies for building plasma, the intent here was to have a collection of external build dependencies to build KDE from kdesrc-build easily installable to help onboarding upstream KDE developers and/or automation.

Wouldn't dnf builddep <packagename> get those for you?

Wouldn't dnf builddep <packagename> get those for you?

I think what they wanted is one meta package that brings in all the packages required for kdesrc-build in one fell swoop.

IIRC, kdesrc-build / kde-builder don't have a static list of dependencies, do they?

Just following up on this -- does the Sig still want to pursue this? @ngraham had communicated that KDE would like to be able to promote a single meta package for onboarding new developers to helping with the KDE stack.

Yes, I think it'd be a good idea to make it easier for KDE developers to develop KDE on Fedora. Perhaps if there's a git repo that contains the things, we could package that as a "metapackage" and use dynamic packaging features to generate the metapackages based on those things.

That is, I'm referring to this feature: https://rpm-software-management.github.io/rpm/manual/dynamic_specs.html

Upstream KDE maintains its dependency list here: https://invent.kde.org/sysadmin/repo-metadata/-/blob/master/distro-dependencies/fedora.ini

Those are then automatically installed through kdesrc-build. I'm not sure how us maintaining the same list downstream would help, if the process still goes through kdesrc-build?

@ngraham

We'll need to refresh this so that the list more closely matches what we pull in for our KDE software builds and eliminate the wildcards, then we can use this to have dynamically generated metapackages based on this data that KDE developers can rely on for getting all the things.

I have a draft PR to update the list there: https://invent.kde.org/sysadmin/repo-metadata/-/merge_requests/392

I have a draft PR to update the list there: https://invent.kde.org/sysadmin/repo-metadata/-/merge_requests/392

Looking at the message it says that this PR needs to be rebased and out of draft to be approved. This entry can probably be untagged with meeting since it's pending action on the PR