Michael J. Knox wrote:
Thorsten Leemhuis wrote:
Ralf Corsepius schrieb:
On Fri, 2006-07-14 at 09:39 +0200, Thorsten Leemhuis wrote:
Not that it matters much, but:
Paul Howarth schrieb:
On Fri, 2006-07-14 at 18:57 +1200, Michael J. Knox wrote:
Ralf Corsepius wrote:
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.
Yes. But intltool is included in some (a lot of?) packages so...
Adding intltool as a
buildreq will automatically pull in XML::Parser.
...will add a package as buildreq that's not used at all during build.
Maybe I should have mentioned here...
"So adding
BuildRequires: perl(XML::Parser)
is IMHO the better solution"
Ok, I will keep this in mind for future packaging. However, the "threat"
of an external perl module being pulled into perl itself would be
possible for any perl module... so are all perl related BuildRequires:
to be perl(Something::Whatever) ?
Yes. This is what you'll find in just about every perl module oackage in
Extras that depends on other modules.
Paul.
--
fedora-extras-list mailing list
fedora-extras-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-extras-list
