XML::Parser, which software is required when (was: Re: [COMMIT LOGREPORT] vanbaal 'service/all/etc defaults.in)

Joost van Baal joostvb at logreport.org
Mon Jun 4 11:14:18 CEST 2001


On Mon, Jun 04, 2001 at 10:53:38AM +0200, Egon Willighagen wrote:
> On Sunday 03 June 2001 16:39, Joost van Baal wrote:
> > Update of /cvsroot/logreport/service/all/etc
> > In directory usw-pr-cvs1:/tmp/cvs-serv29316/all/etc
> >
> > Modified Files:
> > 	defaults.in
> > Log Message:
> > added lr_xml_parser: a simple script to see if we can get XML::Parser to
> >  work, just for testing.  This should not be shipped with the release.
> > lr_db thingies: fixed bug which made them die on first run.
> 
> XML::Parser -> is dit voor offline doeleinden, of als vereiste? want dan kan
> ik hem gebruiken in lr_xml2png enzo...

I am considering using XML::Parser to parse lire reports in xml format.
When merging reports, e.g. to make a weekly overview from daily reports
about one service on one host, using this CPAN module can be very
usefull.  In case one is not interested in merging reports, the module
is not needed.  I believe it would be better not to make the module an
absolute requirement, since it relies on James Clark's XML parser, expat.
It might be some hassle to install this.  (Don't know for sure, though.)
If anybody has got other opinions on this, I'm interested.

Using this parser in lr_xml2png seems logical to me.  A "simple" install
could generate just the ascii reports, as it does now.  For a "full"
install, with pdf reports, merged reports, and pictures, one needs
additional software.

Bye,

Joost


-- 
To UNSUBSCRIBE, email to development-request at logreport.org with a subject of 
"unsubscribe". Trouble? Send an email with subject "help" to 
development-request at logreport.org



More information about the Development mailing list