| From: | "Matt Sergeant" <msergeant [...] startechgroup.co.uk> |
| To: | <bug-XML-SAX [...] rt.cpan.org> |
| Subject: | ParserDetails.ini in @INC |
| Date: | Wed, 23 Jan 2002 09:06:49 -0000 |
Make sure to implement this.
Show quoted text
----- Original Message -----
From: "Ardo van Rangelrooij" <ardo@debian.org>
To: "Perl-Xml (E-mail)" <perl-xml@listserv.activestate.com>
Sent: Wednesday, January 23, 2002 4:01 AM
Subject: Re: ANNOUNCE: XML::SAX 0.05
to
XML::SAX
file.
package,
in
'save_parsers()'
> Matt Sergeant (msergeant@startechgroup.co.uk) wrote:
uploaded
> > Last night I uploaded 0.04, realised I didn't update some docs, so
> > 0.05 shortly thereafter. Changes are:
> >
> > - Some XML::SAX::PurePerl fixes (mostly namespace related, but also now
> > calls set_document_locator as per the SAX spec).
> > - Added a DocumentLocator class which provides a tied hash access sytem
> > the elements of the locator in the spec.
> > - Added remove_parser() to XML::SAX
> >
> > Note that remove_parser() probably doesn't fix all the problems Ardo is
> > reporting, but I think it's a step in the right direction.
> >
> > One thing Ardo suggests is that ParserDetails.ini is part of the
> > distribution, but it's not - it should be a purely install generated
> > Don't know if that helps clarify things for distro builders.
>
> Let me clarify a few things here: It's indeed not a part of the CPAN
> but if I out-of-the-box run 'perl Makefile.PL; make; make install' and
ship
> that, then it is a part of the Debian package. All that I've basically
done
> is move the parser registration from the CPAN package install to the
Debian
> package install (and add parser deregistration to the Debian package
remove).
> And this needs to be done for all parsers (at least in Debian). As part
of
> this move I stubed 'save_parsers()' replacing it (reusing as much as
possible
> of the existing API) with 'save_parsers_debian()' to have
ParserDetails.ini
> created under /etc. XML/SAX/ParserDetails.ini is symlinked to keep
XML::SAX
> working properly.
>
> Adding 'remove_parser()' is very much appreciated. This greatly
simplifies
> the 'update-perl-sax-parsers' script. The next great addition would be
the
> support for being able to indicate to 'load_parsers()' and
'save_parsers()'
> which ParserDetails.ini file to use.
>
problem -
> > Also as far as the "Doesn't allow user-local ParserDetails.ini"
> > this is just alledged. You can have XML/SAX/ParserDetails.ini anywhere
> > @INC.
>
> Well, I'm not a Perl guru, but I only see 'load_parsers()' and
> looking in the directory where 'XML/SAX.pm' is installed. I've not seen
an
> option for either of these subs to indicate to look anywhere else, nor
code to
> look down @INC.
>
> Really, all that is needed is the ability to look down the @INC for one or
more
> ParserDetails.ini files and merge them in a first-come-first-serve order
(similar
> to what 'add_parser()' does) and the above requested ParserDetails.ini
location
> indication options. In Debian we can use the 'update-perl-sax-parsers'
script
> to manage these ParserDetails.ini files: Debian package install/remove
handles
> the parsers under /usr, the local sysadmin the parsers under /usr/local,
and a
> user the parsers in her home directory. Make sure all these are in the
@INC and
> we're in business.
>
> Thanks,
> Ardo
> --
> Ardo van Rangelrooij
> home email: ardo@debian.org
> home page: http://people.debian.org/~ardo
> GnuPG fp: 3B 1F 21 72 00 5C 3A 73 7F 72 DF D9 90 78 47 F9
> _______________________________________________
> Perl-XML mailing list
> Perl-XML@listserv.ActiveState.com
> http://listserv.ActiveState.com/mailman/listinfo/perl-xml
>
> ________________________________________________________________________
> This e-mail has been scanned for all viruses by Star Internet. The
> service is powered by MessageLabs. For more information on a proactive
> anti-virus service working around the clock, around the globe, visit:
> http://www.star.net.uk
> ________________________________________________________________________
>