Re: [PEPr] Call for votes on PEAR::PEAR_PackageUpdate

Hi Bertrand, bertrand Gugger wrote:

Bonjour, Sorry being very late on your proposal. From a cursory review , I would say it's high quality code. I just wonder why the factory does not give back a forced reference, but I guess it's PHP5 related.

I am in PHP 5 mode so I tend to forget about those things :) I will change it to return by reference before the first release.

My wonder is: what does that gives better than PEAR itself or the PEAR_Frontend_xxx things ? I saw the user confirmation, it's a very nice thing I ask since ever, even tunable , better. I fear code duplications / contradictions. Note that I'm not opposed to the package, but just wonder what's really new , I guess I miss something.

That's a good question. PEAR_Frontend_XXX is used to manage all of the PEAR packages installed on your computer. PEAR_PackageUpdate is designed to be embedded in other packages so that they are kept up to date when they are used. For example, if you embed a call to PEAR_PackageUpdate in Benchmark, it can help to make sure that the user's version is up to date. Every time the user runs a benchmark, you package (Benchmark) can check to make sure that the user has the most recent release. If they are working with the most recent release (or at least recent enough for their them, that's what the preferences are for) the script runs as it normally would. If they are working with an outdated version of Benchmark, PEAR_PackageUpdate gives them the chance to get the latest version before they continue. This will help to reduce the number of bogus bugs reported because users won't report bugs that are already fixed in the latest release. It will also make sure that the user has the latest features and implementations. PEAR_PackageUpdate doesn't install or remove packages like PEAR_Frontend_XXX. Nor does it manage all packages. It just keeps one package up to date. -- Scott Mattocks Author of the soon to be published: Pro PHP-GTK http://www.crisscott.com