Description of problem:
yum install perl-Template-Toolkit
dep error nothing provides perl(XML::DOM)
perl-libxml-enno removed from Core as of 20050921
Found this while trying to do the review for Sprog
Any chance this could be fixed soonish?
I don't know much (if anything) about FC packaging rules, but I know the
Template Toolkit and there's no reason for TT to have a dependency on XML::DOM.
TT will always install Template::Plugin::XML::DOM, but will only make use of it
if XML::DOM is installed. You can install TT from CPAN without XML::DOM
installed, so I don't see why it's a requirement for an RPM installation.
The same is true of all of the Template Plugins that are distributed as part of
the standard TT package.
But, without XML::DOM, the Template::Plugin::XML::DOM will not do anything. The
rpm requirements are designed so that when you install TT, you get all the bits
to make it fully functional.
That's true of course. But the same is also true of the dozen or do
Template::Plugin modules that are bundled with TT. I really don't think that you
want to force people to install all of those optional modules as well.
I don't have any firm figures of course, but I suspect that only a tiny
percentage of TT users make use of the XML::DOM plugin. Personally I find the
XML::XPath plugin or the (separately available) XML::LibXML plugin to be much
more useful when I'm processing XML.
When you install TT from CPAN it displays a list of Plugins and tells you which
ones will work (as you have the underlying modules installed) and which other
modules you would need to install in order to activate the other ones. Is it
possible to do something similar during the RPM installation?
This is fallout from bug 128879. FWIW, I don't think it should be "fixed" in
perl-Template-Toolkit, but someone should just package perl-XML-RegExp and
perl-XML-DOM in Extras instead.
I think that the xml-enno/XML::DOM split is a complete red herring. The
perl-Template-Toolkit RPM should not be dependent on other RPMs that aren't
necessary for its use.
(In reply to comment #4)
> This is fallout from bug 128879. FWIW, I don't think it should be "fixed" in
> perl-Template-Toolkit, but someone should just package perl-XML-RegExp and
> perl-XML-DOM in Extras instead.
That sounds perfectly reasonable... I'm all for the least path of resistance
towards a solution.
Spot, are you willing and able to spin up the perl-XML-RegExp and perl-XML-DOM
as part of extras as the near term 'fix'?
More info in bug 128879 comment 9.
Should be fixed now (bug 172331).