Bug 202280 - libogg-devel contains a .pc file but has no dependency on pkgconfig
Summary: libogg-devel contains a .pc file but has no dependency on pkgconfig
Alias: None
Product: Fedora
Classification: Fedora
Component: libogg
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Monty
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2006-08-11 23:52 UTC by Jason Tibbitts
Modified: 2013-10-20 22:42 UTC (History)
3 users (show)

Clone Of:
Last Closed: 2006-08-17 13:41:03 UTC

Attachments (Terms of Use)
Tiny specfile patch to add pkgconfig dependency (534 bytes, patch)
2006-08-11 23:52 UTC, Jason Tibbitts
no flags Details | Diff

Description Jason Tibbitts 2006-08-11 23:52:23 UTC
The summary says it all: libogg-devel includes /usr/lib/pkgconfig/ogg.pc but has
no dependency on pkgconfig.

Comment 1 Jason Tibbitts 2006-08-11 23:52:23 UTC
Created attachment 134073 [details]
Tiny specfile patch to add pkgconfig dependency

Comment 2 Matthias Clasen 2006-08-16 22:22:30 UTC
I don't see why it should. You need pkg-config to use a .pc file, but that
does not mean that every package that installs a .pc file needs a pkg-config
dependency. We don't require cpp for each package that installs a header file,

Comment 3 Jason Tibbitts 2006-08-16 23:42:22 UTC
Well, the primary reason is directory ownership.  libogg-devel cannot own
/usr/lib/pkgconfig because that would be a violation of the prohibition against
needlessly owning directories owned by other packages.  But if it doesn't own
/usr/lib/pkgconfig and doesn't depend on that directory or some package which
provides it (i.e. pkgconfig) then that directory is unowned.

Because it wouldn't hurt to make this a bit more obvious, the packaging
committee voted to add a specific item to the guidelines; see our meeting notes
at http://fedoraproject.org/wiki/Packaging/IRCLog20060706.

Comment 4 Matthias Clasen 2006-08-17 03:02:46 UTC
I'd say a much more reasonable solution would be to let 
/usr/lib/pkgconfig be owned by the filesystem package.

Comment 5 Rex Dieter 2006-08-17 11:27:53 UTC
Matthias, the packaging guidelines are clear on this.  No unowned directories,
period.  As of right now, %{_libdir}/pkgconfig is owned by pkgconfig.  Fix it. 
Besides, .pc files are pretty much useless without pkgconfig, and keep in mind
that pkgconfig is a very small, innocuous package.  Why are you hesitant to make
such a small, simple change?

Now, if you disagree with this policy and/or directory ownerships, you're welcome
(and encouraged) to raise the issue (with the packaging comittee and/orr the
filesystem maintainer), but imo, that should happen *after* this bug is fixed.

Comment 6 Jesse Keating 2006-08-17 11:41:35 UTC
Until such time as the filesystem package owns the %{_libdir}/pkgconfig
directory, this guideline will stand.  If filesystem owns the directory and we
remove the fact that many packages could end up owning it, we can revisit this
issue and possible remove the necessity on pkgconfig for any file that drops a
.pc file.  However the former needs to happen before we discuss the latter.

Comment 7 Matthias Clasen 2006-08-17 13:17:46 UTC
right, we need to do all the work first, before we reconsider :-)

Comment 8 Christopher Stone 2006-08-17 18:51:28 UTC
I would say adding /usr/lib/pkgconfig to filesystem is totally UNreasonable. 
Why would you think this directory blongs there instead?  And even if it did,
you would still be requiring that any package that requires your package also
have to add pkgconfig which is just plain wrong.

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