[pkg-php-pear] MDB2_Schema

[Thomas Müller]

Am Donnerstag, dem 26.04.2012 um 7:13 schrieb Thomas Goirand:
> On 04/25/2012 05:48 PM, Thomas Müller wrote:
> > Hi guys,
> > 
> > Paul and myself are about to package ownCloud for Debian.
> > 
> > ownCloud heavily uses MDB2 and MDB2_Schema.
> > Within our package we will depend on php-mdb2.
> > 
> > But we have no package for MDB2_Schema.
> > 
> > Any plans to provide a package for that?
> > Can we request that? ;-)
> > 
> > 
> > Thanks a lot,
> > 
> > Tom
> > 
> > http://owncloud.org
> > http://pear.php.net/package/MDB2_Schema
> 
> Hi,
> 
> According to:
> http://pear.php.net/package/MDB2_Schema
> 
> this means that we would have to package:
> - http://pear.php.net/package/MDB2_Schema
> - http://pear.php.net/package/XML_DTD
> - http://pear.php.net/package/MDB2
> 
> The main issue that I see is that all of the above 3 packages are
> depending on php-xml-parser:
> http://pear.php.net/package/XML_Parser
> 
> as you can see on this page, XML_Parser has been partially rewrote into
> XML_Parser2. The reason for this is that XML_Parser has loads of issues
> in its classes definitions, meaning that a rewrite and fix breaks a bit
> the API.
> 
> If you want to understand a bit more what happened, I would suggest you
> to do make a diff between XML_Parser and XML_Parser2, and you will see
> how much XML_Parser is broken in its classes definitions. Also, upstream
> author of XML_Parser hasn't been cooperative at all, and the package has
> been taken over by the PEAR QA team for this reason (which lead to the
> writing of XML_Parser2).
> 
> I don't mind working on the packaging of the above 3 PEAR packages, but
> I'm really concern that adding new dependency to an already broken PEAR
> package is going to hurt more than help. Best would be to have as much
> as possible all PEAR package switch to XML_Parser2, but really, I wont
> have much time to work on this.
> 
> So we have 2 choices here:
> - Package MDB2_Schema, XML_DTD and MDB2 to make them available for
> Wheezy quickly with dependency to XML_Parser, live with this, and hope
> that they will switch to XML_Parser2 for Wheezy+1.
> - Try to clean-up things directly, and see if most packages can switch
> to XML_Parser2, so we can totally remove XML_Parser from Debian testing,
> and try to convince upstream authors of said PEAR packages to switch as
> well.
> 
> Any thoughts?
> 
> Cheers,
> 
> Thomas

Hi Thomas,

thanks a lot for your detailed email.

What a mess! ;-)

I would really love to walk the clean path, but unfortunately we have already a lot to do e.g. 
package SabreDAV or find someone, who can do it.

I'd vote for first choice just to gain momentum and get things done.

@Paul: your opinion on this?

THX a lot,

Tom