Ralf Corsepius schrieb:
On Fri, 2006-07-14 at 11:00 +0200, 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"
...because I fail to understand what you want to tell me with:
I and tell you:
Seems you didn't get what I was up to. Seems I didn't explain it well.
This...
Adding BuildRequires: perl(XML::Parser) to packages using intltool is
non-sense, because BuildRequires: intltool must already pull in
perl(XML::Parser). If this doesn't work, intltool's packaging is broken.
...of course is correct if the external intltool is used. But if the
packages includes intltool already then
BuildRequires: perl(XML::Parser)
avoids the installation of one unnecessary BR (because the systems
intltool is unnecessary in this case).
But as I said: It doesn't matter that much. So let's stop this thread here.
CU
thl
--
fedora-extras-list mailing list
fedora-extras-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-extras-list
