On Fri, 2006-07-14 at 18:57 +1200, Michael J. Knox wrote: > Ralf Corsepius wrote: > > On Fri, 2006-07-14 at 18:17 +1200, Michael J. Knox wrote: > >> Parag N(पराग़) wrote: > >>> Hi, > >>> While reviewing some packages i am getting following errors in mock > >>> build for rawhide repository > >>> > >>> checking for intltool >= 0.18... 0.34.1 found > >>> checking for perl... /usr/bin/perl > >>> checking for XML::Parser... configure: error: XML::Parser perl module > >>> is required for intltool > >>> error: Bad exit status from /var/tmp/rpm-tmp.20633 (%build) > >>> > >>> What am i missing that leads mock build to fail? I am doing mock build > >>> using local rawhide mirror repository. > >> You need: > >> > >> BuildRequires: perl-XML-Parser > > Nope. > > > > 1. If a package wants the XML::Parser module, it should > > BuildRequires: perl(XML::Parser) > > > > > Well, I have seen it done both ways and there has not been people saying > different. Oh well. The XML::Parser module might some day get swallowed up into the main perl package. If that happens, packages buildrequiring perl(XML::Parser) will continue to build OK, and packages buildrequiring perl-XML-Parser will not (the main perl package would provide the former but not the latter). In virtually all of these cases, the right thing to add as a buildreq is actually intltool really, since XML::Parser is being checked for in the configure script to ensure that intltool will work. Adding intltool as a buildreq will automatically pull in XML::Parser. Paul. -- fedora-extras-list mailing list fedora-extras-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-extras-list
