Re: solution for those depending on PEAR packages with non-PEAR apps

Greg Beaver wrote:

Hi, Lukas and others have mentioned a problem that applications have when depending on a PEAR package: if a critical bug is found, and the maintainer of the PEAR package is slow to release a new version, then it is very difficult to get a patched version of the package onto client's computers unless you patch it by hand, or instruct them to do the awkward:

This is an awesome idea. Good call again Greg :)

<dependencies> .... <package> <name>Foo</name> <channel>pear.php.net</channel> <min>1.2.0.1</min> <patch>http://www.yourhost.example.com/Foo-1.2.0.1</patch> </package>

I'm not sure about this though. Imagine this scenario: 1) Dev finds bug in Foo-1.2 2) Dev fixes bug 3) Dev release patch as Foo-1.3 4 the original developer of Foo releases 1.3 how does it know to upgrade? It needs to be handled differently, you need to specify what package version you're patching so that we can tell when its upgraded. That way your 1.3 doesn't conflict with the original developers 1.3 We can enforce a naming scheme for this, I think. i.e. <patch for="1.2"> and the patch package must be called 1.2pX where X is a version, 1, 2, 3, 12, no periods. Is it possible in Package2.xml to specify a dep of > 1.2? - Davey