3 ms·
> We hit this in the subsurface project too. We had a couple of libraries that nobody else used. Literally nobody. But the Fedora policy meant that a Fedora pac
by rwmj 6y ago
> We hit this in the subsurface project too. We had a couple of libraries that nobody else used. Literally nobody. But the Fedora policy meant that a Fedora package had to go the extra mile to make those other libraries be shared libraries,
I'm a Fedora packager and I'm not sure what he's talking about here. If a single package uses some code then there's no requirement to make that code into a shared library.
- exciteabletom 6y agoThe Fedora docs[0] say: > Packages including libraries SHOULD exclude static libs as far as possible > In general, packagers SHOULD NOT ship static libraries. [0] https://docs.fedoraproject.org/en-US/packaging-guidelines/#packaging-static-libraries https://docs.fedoraproject.org/en-US/packaging-guidelines/#p...
- rwmj 6y agoBut that's if the libraries are going to be used by another package (and even then it's not a prohibition - packagers should use common sense). Linus said this applied to a single package so it wouldn't need to ship *.a files at all, as everything would presumably be linked to binaries. I'm going to check out this subsurface diving program to find out what really happened here.