Description of problem: The static library should be in a ruby-static subpackage. In my opinion it could be called libruby.a (maybe with a link to libruby-static.a for backward compatibility) This package should Provides: ruby-libs-static = %{version}-%{release} if you want to be backward compatible. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
See Bug#428384. -devel package requires the static library to get it working anyway. I don't think having separate package for the static library does help something really in this case.
I have seen where the static lib is put in the link, but is the static lib really needed to link against libruby?
requested by Jens Petersen (#27995)
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This is already fixed (see comments in bug 428384)