Bug 170716

Summary:	Missing dep perl(XML::DOM), need perl-XML-RegExp and perl-XML-DOM in Extras
Product:	[Fedora] Fedora	Reporter:	Jef Spaleta <jspaleta>
Component:	perl-Template-Toolkit	Assignee:	Tom "spot" Callaway <tcallawa>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	dave, extras-qa, scop, wtogami
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-11-09 21:39:41 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	172331
Bug Blocks:	162161

Description Jef Spaleta 2005-10-13 23:48:11 UTC

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 
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=166255

Any chance this could be fixed soonish?
-jef

Comment 1 Dave Cross 2005-10-14 18:38:30 UTC

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.

Dave...

Comment 2 Tom "spot" Callaway 2005-10-14 18:56:58 UTC

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.

Comment 3 Dave Cross 2005-10-15 06:23:08 UTC

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?

Dave...

Comment 4 Ville Skyttä 2005-10-15 08:25:57 UTC

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.

Comment 5 Dave Cross 2005-10-15 09:48:46 UTC

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.

Dave...

Comment 6 Jef Spaleta 2005-10-15 14:17:33 UTC

(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'?  

-jef

Comment 7 Ville Skyttä 2005-10-27 19:09:38 UTC

More info in bug 128879 comment 9.

Comment 8 Ville Skyttä 2005-11-09 21:39:41 UTC

Should be fixed now (bug 172331).