Hmm, now I understand the complaints even more. Seems like I can't install a debconf "module" under Perl 5.6.0 because there IS NO DEBCONF MODULE! Why would someone want to hard code pathnames into the Makefile instead of providing a Makefile.pl just like everyone else? Sure, someone put a $(prefix) in front of everything, but that's practically useless.
I would have thought that the deb Perl modules would have been made "standard" so that anyone could upgrade Perl at their own convienance, given a respectable amount of experience, and not be put in the position of being prevented from doing so. It's a little too much like being stuck in the position of someone being forced to reply on Microsoft to fix bugs and/or upgrade system features because it's a closed-source binary-only OS. Is there anything that can be done to use Perl in the standard way if it's going to be used at all for package maintenance or other system functions? Fred Reimer On Sat, 15 Jul 2000 14:58:27 Fred Reimer wrote: > > Well, I wouldn't use quite so strong words, but I don't understand > myself why Debian has to make custom deb packages for CPAN modules. > Wouldn't it be workable to create deb "packages" that were more like > installation helper scripts instead of the binaries themselves? So you > select a package and when it was installed your system would run > something like "perl -MCPAN -e 'install XML::XPath'" > > Part of the strength of Perl is that you can relatively easily install > and remove packages. Mixing this ability with binary packages, in > either a deb or rpm type system, just makes it harder to maintain two > different "systems." > > Fred Reimer > > > On Sat, 15 Jul 2000 09:33:11 Michael Koehne wrote: > > Moin Fabien Ninoles, > > > > > I also just upload a XPath perl module which included a useful > > > script (heavily modified by me and contribute back to the > > > upstream author) for querying XML document using XPath > > > pointers (truely useful for XML scripting!). > > > > If you realy think, that your script is usefull : > > > > Make it become a module conforming to Perl coding standard > > and upload it to CPAN. > > > > I realy dislike the way Debian !IGNORES! CPAN. > > > > e.g. debconf, debhelper, netbase and dpkg-perl deserve their > > Perl modules to become either !DELETED! or !REWRITTEN! to > > conform to Perl coding standard. > > > > Those !BROKEN! modules are the main reason, that its impossible > > to throw Perl 5.005 in the trashcan, and to use Perl 5.6 as a > > default perl for Debian. To use Perl 5.6 is a requirement for > > any serious XML work, because of `use utf8;`. So Debian is quite > > useless for XML, because of its dependencies to !BROKEN! modules. > > > > I would realy deprecicate, if you upload a version of XML::XPath > > containing something not in the CPAN module! > > > > > I'm looking forward to add some little formatting features to the result > > > so that people can use it as an intermediate between simple XPath queries > > > and XSLT. Think of it as a simpler awk for xml (extract xml informations > > > and reformat the output in one tool). > > > > take a look at XML::Filter::Digest. This is using XML::XPath::Builder, > > and its own light weight script to query XPath on XML documents. > > > > Bye Michael > > -- > > mailto:[EMAIL PROTECTED] UNA:+.? > 'CED+2+:::Linux:2.2.14'UNZ+1' > > http://www.xml-edifact.org/ CETERUM CENSEO MSDOS ESSE DELENDAM > > > > > > -- > > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] > > > > > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > >
