Description of problem:
Static bzip2 libraries are not available.
Version-Release number of selected component (if applicable):
All versions after bzip2-1.0.5-5.fc11
The presence of a bzip2-static package containing /usr/lib64/libbz2.a
Related to https://bugzilla.redhat.com/show_bug.cgi?id=486593. The solution to removing the static libraries from -devel package was to just remove them entirely. The static libraries should still be made available, however, as a seperate bzip2-static package.
can you justify, why you need static library? Dynamic one is not enough?
Really the same reason any static libraries are needed: they're useful to have for software development. It's also a matter of consistency for the core system compression as zlib-static and xz-static are available. The only people that really use the foo-static packages are C and C++ developers but they're useful to have around to keep your dependencies consistent. Usually static libs are nice to have to make the executables you build portable to Linux systems.
It just seems arbitrary to have them available for some system packages and not others.
"In general, packagers are strongly encouraged not to ship static libs unless a compelling reason exists."
Still, is there a problem using the dynamic one? For development, you can locally build static bzip2 library and use it (edit spec file, can send you a patch).
It can be nice to have them on your system but it does not mean they should be there. Besides, if I rebuild the bzip2 package for some security issue, you will have to rebuild your package too. How can I know you will get this information? Via dynamic library, this is just a matter of package update.
Still don't see a reason why there should be the static subpackage. If you believe I am wrong, please, email email@example.com and discuss this issue with them.