Bug 609858

Summary:	avarice : does not adhere to Static Library Packaging Guidelines
Product:	[Fedora] Fedora	Reporter:	Michael Schwendt <bugs.michael>
Component:	avarice	Assignee:	Lucian Langa <lucilanga>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	rawhide	CC:	lucilanga
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-07-01 19:42:22 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:

Description Michael Schwendt 2010-07-01 10:40:15 UTC

avarice-2.10-4.fc14.src
is missing
BuildRequires: binutils-static

[...]

https://fedoraproject.org/wiki/Packaging:Guidelines#Packaging_Static_Libraries_2

If a library you depend on only provides a static version your package can link against it provided that you BuildRequire the *-static subpackage. Packagers in such a situation should be aware that if a shared library becomes available, that you should adjust your package to use the shared library.

Comment 1 Lucian Langa 2010-07-01 15:05:23 UTC

I'm pretty confused here,
binutils-devel was merged in binutils-static now binutils-static has been renamed to binutils-devel. Isn't now the same think using BR binutils-devel ?

Comment 2 Michael Schwendt 2010-07-01 18:26:36 UTC

binutils-devel enforces static linking via ld scripts (in the *.so files). So, as long as you can only link statically with binutils' libs, the quoted packaging guidelines ask you to BuildRequires binutils-static (even if binutils-devel currently gives you the same package). This is for tracking-purposes.