Bug 175835 - would like static libs (*.a) put back in
would like static libs (*.a) put back in
Status: CLOSED WONTFIX
Product: Fedora
Classification: Fedora
Component: libjpeg (Show other bugs)
5
All Linux
medium Severity medium
: ---
: ---
Assigned To: Matthias Clasen
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-12-15 11:56 EST by Peter Quiring
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-12-15 12:04:40 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Peter Quiring 2005-12-15 11:56:38 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051211 Fedora/1.5-1.1 Firefox/1.5

Description of problem:
I noticed in ticket #145971 that the static libs from jpeg-devel were removed.  I need these libs for my projects.  I prefer to build projects with -static option to increase their portablility.  As a third party vendor this is essential.

Please put back the *.a files, and please don't remove any others.

Thanks.


Version-Release number of selected component (if applicable):
libjpeg-devel-6b-36

How reproducible:
Always

Steps to Reproduce:
1.Install jpeg-devel.
2.Build -static projects.
3.Fails (ljpeg not found)
  

Actual Results:  library not found.

Expected Results:  build project as before.

Additional info:
Comment 1 Matthias Clasen 2005-12-15 12:04:40 EST
No.

To cite the Fedora packaging guidelines:

Packages including libraries should exclude static libs as far as possible (eg
by configuring with --disable-static). Static libraries should only be included
in exceptional circumstances. Also applications linking against libraries should
as far as possible link against shared libraries not static versions.


Bring it up on fedora-devel, if you feel strongly about it.

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