Re: [RFC] Deprecate PEAR/PECL & Replace with composer/pickle
| From: | Tony Marston | Date: | Wed, 07 Sep 2016 07:52:09 +0000 |
| Subject: | Re: [RFC] Deprecate PEAR/PECL & Replace with composer/pickle | ||
| References: | 1 2 3 4 5 6 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-95713@lists.php.net to get a copy of this message | ||
"Pierre Joye" wrote in message news:CAEZPtU6aHYb9HsNXbXWp9q9PMoLYiJp=N1rjmspoFmHBEbDHxg@mail.gmail.com...
Hi Tony, On Tue, Sep 6, 2016 at 2:17 PM, Tony Marston <TonyMarston@hotmail.com> wrote:Typical. You create a useful tool, get your users hooked, then walk away and leave them dangling. -- Tony Marston"Niklas Keller" wrote in message news:CANUQDCjeH45_2aEq74CCEOY4xc3xJ0o_+yRQ2NVy0K2VdOXFBQ@mail.gmail.com...On 02/09/2016 20:32, Davey Shafik wrote:Tony Marston <TonyMarston@hotmail.com> schrieb am So., 4. Sep. 2016, 10:38:"Rowan Collins" wrote in message news:b3bd7acf-a525-d921-1b1b-64ccf94b858b@gmail.com...Hi Davey, I think this is a sensible idea. It basically accepts the reality thatI'd like to introduce a new RFC to deprecate pear/pecl (in 7.2, and remove in 8.0), as well as add composer/pickle (optional in 7.2, default in 7.3+) in their place. https://wiki.php.net/rfc/deprecate-pear-include-composeris no longer the main place new users of PHP should look for 3rd-party code. Thinking about the responses so far, I thought it would be useful to enumerate just what PEAR is, and what is being proposed for removal. It might even be worth adding a version of this to the RFC, in case itPEARa wider audience who won't see this discussion. As I understand it, PEAR is: A1) A command-line package management tool for installing and updating packages of PHP code over the Internet.reachesIt has, whether you need it or not is not really relevant to this discussion.PEAR does not have a version control system. My software has an SVN repository, but that is totally unconnected with PEAR. My choice of editor has no bearing on the issue.Incorrect. There is a web interface which I use EXCLUSIVELY to maintain the contents of my PEAR library.You only work in a web interface instead of an editor and version control system?I use the web interface to maintain PEAR on my local machine, and my hosting companies provide a web interface in their control panels.Happy to see there are still users for this tool, Christian and I had good fun writing it. Also you should know that this package is dead, it has no acttve maintainer (I was the last one) and has some limitations from to begin with, also was very handy at time especially for shared hosting without shell access.