Where are packages for atomic variants defined?

When using an atomic desktop (Silverblue in my case), I’m using an ostree image. This image needs to be created somewhere. At this place, there needs to be a list of packages defined that end up being the “leaf” packages in the atomic desktop’s base layer. Where is this list defined, in a git repo?

I’m asking because there are leaf packages in my Silverblue base layer that I’m wondering whether they should be there, for example braille-printer-app. rpmreaper shows me that it is a leaf package, i.e., it is not pulled in by something like fedora-release-silverblue as dependency, so it needs to have been installed from an explicit list somewhere.

The braille-printer-app is recommended by the cups-filters, and recommended packages are usually installed by default.

From rpm -q --recommends cups-filters

braille-printer-app

Recommended packages are still leaves.

Thanks for this info!

There are a lot more “leaf” packages, for many of which rpm -q --recommends [packagename] doesn’t give anything. Here is a list of packages I’d find interesting:

xset
braille-printer-app
libwnck3
python3-boto3
python3-botocore
python3-httpx
python3-s3transfer
python3-urllib3+socks
python3-httpcore
mod_lua
cpp
buildah
qemu-user-static-aarch64
python3-perf
cracklib-dicts
qadwaitadecorations-qt5
gstreamer1-plugins-good-qt

(Some of them are probably installed on my layered packages, not in the base layer)

For some, rpm -q --supplements [packagename] also gives details, but how about the others?

EDIT
This comment explains that, however it doesn’t provide a solution: rpm -q --recommends only works for capabilities, it will be incomplete for package names. However, the suggested solution with rpm --test -e doesn’t work for my case, because it doesn’t care about weak dependencies.

The reverse relationship of --recommends is --whatrecommends, for example

rpm -q --whatrecommends cracklib-dicts

Other leaf packages may be included because the were included in a group. In the end, the list of packages to be included in an edition seems sometime to be arbitrary, and you may find packages include which you would never use, and vice-versa.

You can file issues about package inclusion here: Making sure you're not a bot!

Sometimes package dependencies change and new packages get pulled in unexpectedly, so it is good to raise concerns and discuss.