Bug 454121 - static lib should be in a separate -static subpackage
static lib should be in a separate -static subpackage
Product: Fedora
Classification: Fedora
Component: ruby (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Jeroen van Meeuwen
Fedora Extras Quality Assurance
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2008-07-04 17:20 EDT by Patrice Dumas
Modified: 2010-01-22 02:51 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-01-22 02:51:52 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Patrice Dumas 2008-07-04 17:20:24 EDT
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:
Actual results:

Expected results:

Additional info:
Comment 1 Akira TAGOH 2008-07-06 20:48:11 EDT
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.
Comment 2 Patrice Dumas 2008-07-08 08:12:18 EDT
I have seen where the static lib is put in the link, but is the static
lib really needed to link against libruby?
Comment 3 Tony Fu 2008-09-09 23:11:05 EDT
requested by Jens Petersen (#27995)
Comment 4 Fedora Admin XMLRPC Client 2009-01-30 07:44:53 EST
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 5 Mamoru TASAKA 2010-01-22 02:51:52 EST
This is already fixed (see comments in bug 428384)

Note You need to log in before you can comment on or make changes to this bug.