Bug 454121
| Summary: | static lib should be in a separate -static subpackage | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Patrice Dumas <pertusus> |
| Component: | ruby | Assignee: | Jeroen van Meeuwen <vanmeeuwen+fedora> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | rawhide | CC: | tagoh |
| Target Milestone: | --- | Keywords: | FutureFeature |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-01-22 07:51:52 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
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) |
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: