Created attachment 134073 [details]
Tiny specfile patch to add pkgconfig dependency

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,
either...

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.

I'd say a much more reasonable solution would be to let 
/usr/lib/pkgconfig be owned by the filesystem package.

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.

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.

right, we need to do all the work first, before we reconsider :-)

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.