Matt Domsch wrote:
On Wed, Jun 14, 2006 at 09:59:32PM +0100, Paul wrote:
xsp paul@xxxxxxxxxxxxxxxxxxxxxx
I can't find a problem with xsp - it builds on the buildsys without
problems
checking for pkg-config... no
configure: error: You need to install pkg-config
pkgconfig will (very soon) no longer be included in the standard
buildroot on the Extras buildsys. It's still in there today, but my
report is a precursor of failures to come. :-)
BuildRequires: pkgconfig
will be necessary for apps that call it.
In most cases I would disagree with this. pkgconfig should be a dep of
any package that provides a .pc file, which would result in pkgconfig
being pulled in by the normal buildreqs of most packages (-devel
packages for required libraries).
However, in this particular case, not a single -devel package is a
buildreq, yet for reasons best known to the upstream author, the
configure script checks for pkgconfig.
As it happens, two .pc files are present in the (i386) root when this
package gets built:
libgdiplus.pc (from libgdiplus)
devmapper.pc (from device-mapper)
If these were packages being reviewed for Extras, they would be required
to split off a -devel subpackage, put the .pc file in that package and
add a dep of pkgconfig for the -devel package. Is there any reason why
this shouldn't apply in Core too?
As for xsp, it'll need a buildreq of pkgconfig until such time as
upstream stops checking for it (if ever).
Paul.
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
