Re: [RFC] Deprecate PEAR/PECL & Replace with composer/pickle

On 04/09/2016 09:38, Tony Marston wrote:

A1) A command-line package management tool for installing and updating packages of PHP code over the Internet.

Incorrect. There is a web interface which I use EXCLUSIVELY to maintain the contents of my PEAR library.

Do you mean there's an HTML control panel for installing and removing PEAR packages from a server? I wasn't aware of that, and would be happy to add it as an additional point in list A. Could you post a link to the documentation for it? Is it currently bundled with the official php.net releases? If so, then we should look into how widely used it is. If not, it is in the same category as pear.php.net, the coding style, and the libraries already written, i.e. it won't actually be affected by this RFC at all. Incidentally, it's tricky to do the same thing with Composer, because it's mostly built around the idea of the dependencies as part of the code, i.e. separate for each project, rather than as part of the server setup. However, you can use it to install packages to a global shared path, I believe, so if there was interest, somebody could make a UI for doing that. Regards, -- Rowan Collins [IMSoP]