Bug 556064 - libcdio : does not adhere to Static Library Packaging Guidelines
Summary: libcdio : does not adhere to Static Library Packaging Guidelines
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: libcdio
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Adrian Reber
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-16 14:46 UTC by Michael Schwendt
Modified: 2010-01-28 10:53 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-01-28 10:53:33 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Michael Schwendt 2010-01-16 14:46:27 UTC
The package is in need of an update because it does not adhere to
the guidelines for packaging static libraries:

  http://fedoraproject.org/wiki/Packaging:Guidelines#Packaging_Static_Libraries

The -devel package contains both the shared and the static build of
a library. That makes it possible to link statically with the -devel
package as a build requirement instead of having to build-require a
special-purpose -static subpackage.

Correct would be to either disable/delete the static libraries at
build-time, or to %exclude them in the %files section, or to split off
a -static subpackage (if there is a compelling reason as why the static
libs should be made available).

Please consult the guidelines for the details.

[...]

libcdio-devel
    /usr/lib/libcdio++.so  <=>  /usr/lib/libcdio++.a
    /usr/lib/libcdio.so  <=>  /usr/lib/libcdio.a
    /usr/lib/libcdio_cdda.so  <=>  /usr/lib/libcdio_cdda.a
    /usr/lib/libcdio_paranoia.so  <=>  /usr/lib/libcdio_paranoia.a
    /usr/lib/libiso9660++.so  <=>  /usr/lib/libiso9660++.a
    /usr/lib/libiso9660.so  <=>  /usr/lib/libiso9660.a
    /usr/lib/libudf.so  <=>  /usr/lib/libudf.a

Comment 1 Adrian Reber 2010-01-28 10:53:33 UTC
Thanks. Fixed in the development branch.


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