Re: deprecating xml-rpc and package.xml 1.0

Lukas Kahwe Smith wrote:

Hi, two more questions .. 1) The MDB2 drivers usually require a specific MDB2 version. If I import the dependencies, how do I overwrite them later on? Do I just add a dependency on MDB2 and it will automatically overwrite the one that was imported?

Hi Lukas, Actually, this question is one of the primary reasons that I don't import dependencies, as they will be duplicated. I use clearDeps() followed by a series of dependency adding functions. A good example of this is the script for Chiara_PEAR_Server http://websvn.bluga.net/wsvn/PEAR_Server/trunk/makepackage.php?op=file&rev=0&sc=0

2) Another thing I might decide to do is set some flags in the MDB2 package that warn or even prevent MDB2 versions to be run with incompatible versions of the drivers. So for example a new MDB2 release may fix some issue, so someone upgrades MDB2. However that same release changed some internal structures, which also require a driver update. How to do this using PFM/package.xml v2 magic?

you would use a conflicts dependency. This is basically a negation, and is demonstrated in PEAR's own package2.xml http://cvs.php.net/viewvc.cgi/pear-core/package2.xml?revision=1.292&view=markup You can't yet create this with PFM because I forgot to update the signature of the core PEAR method that does this: http://pear.php.net/package/PEAR/docs/1.5.0a1/PEAR/PEAR_PackageFile_v2_rw.html#methodaddConflictingPackageDepWithChannel As you can see, versioning info can't be passed in. Time to open a bug! This will get into 1.5.0a2. Greg