Bug 148973

Summary:	rpm should have BuildRequires dependency on libselinux version
Product:	Red Hat Enterprise Linux 4	Reporter:	Jos Vos <jos>
Component:	rpm	Assignee:	Jeff Johnson <jbj>
Status:	CLOSED DEFERRED	QA Contact:	Mike McLean <mikem>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.0	CC:	nobody+pnasrat
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:	2005-02-20 19:14:53 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 Jos Vos 2005-02-17 16:20:00 UTC

Description of problem:
Building the rpm package depends on newer versions of libselinux,
otherwise it complains about an undefined reference "rpm_execcon". 
The rpm src.rpm should contain a BuildRequires dependency for the
correct version of the libselinux (or libselinux-devel?) package.

Version-Release number of selected component (if applicable):
4.3.3-7_nonptl

Comment 1 Jos Vos 2005-02-17 20:53:24 UTC

*** Bug 148982 has been marked as a duplicate of this bug. ***

Comment 2 Jeff Johnson 2005-02-20 19:14:53 UTC

A (necessary imho) ABI change like rpm_execcon cannot be
properly tracked through build dependencies.

Adding a build dependency fo now isn't the right
solution either, as libselinux development is
happening much more quickly than rpm development.
So any build dependency added today is predicatbly
going to rot when libselinux changes and rpm does not.

A more general fix, using dlopen rather than the
traditional (and overly stiff and complex imho)
solution is needed so that rpm "works" with and
without libselinux, either enabled/disabled, strict/targeted.

These are intrinsically run-time attributes that no build
dependency can adequately solve.

Defeered unti then ...