Re: Buggy package.xml files

--On October 19, 2006 1:26:54 PM +0200 Christian Weiske <cweiske@cweiske.de> wrote: > From: Christian Weiske <cweiske@cweiske.de> > To: PEAR Dev List <pear-dev@lists.php.net> > Subject: [PEAR-DEV] Buggy package.xml files > Date-Sent: October 19, 2006 7:26:54 AM > > Today I tried to read the package.xml files in PEAR CVS with DOMXml. > Most read without problems, but some use undefined entities or are even > not well-formed: thoughts for everyone: Do we have a place where we're keeping/collecting handy tools for the developers? A place that says "try this tool to check your package XML" (w/ instructs on where to get it from CVS), and "try this tool to check your docbook coverage" etc... Or maybe an area for developers to "drop your candidate package here" and then pearweb chews on it for them and spits out commentary. I don't think pearweb should be asked to automagically examine a zillion things (like package XML, docbook coverage, CS, etc) when you put up a new versio of a package. But it would be interesting if there was a way to have it run a slew of things and spit out a list of "PEAR suggests the following improvements to your package..." ? -c