Re: PEAR-1.4.0a2 Bugs

Sara Golemon wrote:

#1) pear convert produces a <package> tag containing a malformed parameter: 0="xsi:schemaLocation&apos; =&gt; &apos;http://pear.php.net/dtd/tasks-1.0 http://pear.php.net/dtd/tasks-1.0.xsd http://pear.php.net/dtd/package-2.0 http://pear.php.net/dtd/package-2.0.xsd" I simply ommitted this in my recent release.

I will fix this. Please open a bug for any bugs you find, so I don't forget.

#2) <release/> forces X.Y.Z version numbering, <api/> does not. Forcing an arbitrary numbering scheme is bad enough, but not being inconsistent about it is silly.

I will change that to a warning rather than an error. The numbering scheme is required for PEAR packages, it is not arbitrary. As I said, I am at your service, I am happy to fix any problems encountered. I understand that there will be some growing pains as things move forward, it is my job to minimize them. Please continue to report issues as they come up through the bug tracker.

#3) PEAR-1.4.0 is alpha: Why, oh why, oh why put a requirement on pecl.php.net to use a tool which isn't even marked stable???

Releasing through pear.php.net will always work for pecl devs who don't feel comfortable with the switch until it is stable. The main problem is that there is a chicken and egg situation - pecl will never switch to a new channel and in addition nobody can use the package.xml 2.0 unless pearweb/peclweb is up-to-date on this.

#4) package2.xml is undocumented. While efforts to blog the format are admirable, they are not a manual replacement.

This is on the immediate todo list, as you can probably imagine. Note that the .xsd in http://pear.php.net/dtd/package-2.0.xsd is a real file that can be examined using most .xsd processors. Eclipse has trouble for some reason (at least my version), XMLSpy does not. Again, I am at your service. Greg