On Thu, Jul 31, 2003 at 06:42:41PM +0300, Ville Skyttä wrote:
If you peek at the affected files, you'll see that they actually
are not
"included" as far as rpm is concerned. rpm looks at the "package
foo"
statements when building the list of Provides, and "use/require foo" for
Requires.
Ah yes, ok, then I shouldn't blame rpm's scripts.
Those files do not have a package of their own, instead they blend
into
the XML::SAX::PurePerl package. And perl allows one to use() them using
the fully qualified, "fake" package name (based on the dir structure, I
believe).
What about packaging XML-SAX-PurePerl? Shouldn't that solve the
problem? I have to admit I don't know much about this area, but
I needed XML-SAX because it is required by XML-LibXML.
--
-- Jos Vos <jos(a)xos.nl>
-- X/OS Experts in Open Systems BV | Phone: +31 20 6938364
-- Amsterdam, The Netherlands | Fax: +31 20 6948204