Can you explain why the few kilobytes of the other files are a problem?

It's not the files, but the dependencies that those files pull in -- cmake and many perl packages.

See https://bugzilla.redhat.com/show_bug.cgi?id=2023435 for more info. Installing nss_wrapper to a container pulls in 100MB at the end:

podman run -ti --rm fedora bash -c 'yum install -y nss_wrapper'
...
Install  78 Packages
...
Installed size: 109 M

nss_wrapper is a devel package and the files are normally needed to find the location for preloading it.

I would like to keep the library and manpage together in the main package!

The perl script could go into a nss_wrapper-tools package.

Now the question is where to put the cmake files. Maybe in a nss_wrapper-pkg subpackage together with the pkgconfig file and then recommend to install it?

Any other suggestions?

My first idea was to introduce nss_wrapper-devel -- wouldn't that be a good new home for both, the perl script and cmake files?

Hmm, then we need to create a devel package for all wrappers to be consistent.

Ah, I didn't realize there are more wrappers. It doesn't seem to be worth such a big change that would affect many depended packages.

Making the impact on depended packages invisible was the reason why I suggested to put just the library into a separate sub-package. It would effectively not change anything that would still pull in nss_wrapper package.

I think that detaching a library to an extra sub-package, so it can be installed as a stand-alone component when needed, is actually quite common practice across various packages in Fedora. Couldn't you maybe re-consider that approach?

Lets go with this for now.

Thanks!

I'm not able to build as it looks like the builtroot for (x86_64) is broken (openssl libcrypto.so issue)