Re: Pyrus: Installation of pear/validate-beta fails: invalid package

On 2010-03-11, at 11:34 AM, Helgi Þormar Þorbjörnsson wrote: > Hi, > > Those are all required to generate information for the channel servers. Look at any package > managers out there and you will see very similar information in their package format. > For help with maintaining package.xml files I would advice you to use > http://pear.php.net/package/pear_packagefilemanager2 as it allows > you to have a 20 lines PHP script to maintain and update the files. I've looked at this, but there's no documentation. Since I already use Phing as well, I tried to use their built in generator (which uses pear_packagefilemanager2), but this suddenly broke after a new release. I ended up just copy-pasting a package.xml file from the documentation and just generate the xml 'by hand'. (http://code.google.com/p/sabredav/source/browse/bin/pearpackage2.php) No biggie, but the experience of having to do this just made me think that package.xml could probably be a little simpler. KISS principal basically.. Rather than requiring all the information that could possibly be relevant, what is the absolute minimum you need? Is my (the maintainer) email address really one of them? Perhaps requirements for packages *on* pear.php.net could be stricter. > However ... Pyrus will make things all that much easier to do :) Links to said explanations on > how Pyrus does things elude me at the moment but it does things in a fantastically easy way. I've been hearing a lot about Pyrus, and I'll definitely be doing a switch soon too =) By no means I'd want to sound negative, these were just my general feelings.. which might be useful to you, or not.. doesn't matter Evert