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

2016-09-04 Thread Stanislav Malyshev
Hi! > I think there is value in reducing the number of ‘bundled’ things, > particularly given that Debian (and thus Ubuntu), Centos and OS X all > distribute PEAR/PECL as a separate package. On the Linux distro's > it’s a separate (but possibly “recommended” by php-cli etc) package. > On OSX there

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

2016-09-04 Thread Stephen Reay
> On 5 Sep 2016, at 11:19, Stanislav Malyshev wrote: > > Hi! > >> I'd like to introduce a new RFC to deprecate pear/pecl (in 7.2, and remove > > What would be achieved by this? I'm not sure about status of PEAR - > frankly, didn't touch it for a long time - but if composer replaces most > of i

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

2016-09-04 Thread Stanislav Malyshev
Hi! > I'd like to introduce a new RFC to deprecate pear/pecl (in 7.2, and remove What would be achieved by this? I'm not sure about status of PEAR - frankly, didn't touch it for a long time - but if composer replaces most of it, it may be ok to remove by-default install of pear tools. Though I'm

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

2016-09-04 Thread Stanislav Malyshev
Hi! > Incorrect. There is a web interface which I use EXCLUSIVELY to maintain > the contents of my PEAR library. Any proposed replacement which does not > have a web interface I'm afraid is totally unacceptable. Command line > interfaces went out of fashion when the Windows OS was first released,

Re: [PHP-DEV] RFC - Immutable classes

2016-09-04 Thread Michał Brzuchalski
2016-09-04 22:38 GMT+02:00 Fleshgrinder : > On 9/4/2016 2:29 PM, Michał Brzuchalski wrote: > >> Providing `mutator` | `mut` keyword as method modifier sounds liek a > good > >> idea, > >> althought passing `$clone` parameter as first additional param could > break > >> method declaration and would

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

2016-09-04 Thread James Gilliland
On Sun, Sep 4, 2016, 7:09 PM Ferenc Kovacs wrote: > 2016. szept. 2. 21:58 ezt írta ("James Gilliland" ): > > > > On Fri, Sep 2, 2016 at 2:33 PM Davey Shafik wrote: > > > > > Hi internals, > > > > > > I'd like to introduce a new RFC to deprecate pear/pecl (in 7.2, and > remove > > > in 8.0), as w

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

2016-09-04 Thread Ferenc Kovacs
2016. szept. 2. 21:58 ezt írta ("James Gilliland" ): > > On Fri, Sep 2, 2016 at 2:33 PM Davey Shafik wrote: > > > Hi internals, > > > > I'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 t

Re: [PHP-DEV] RFC - Immutable classes

2016-09-04 Thread Fleshgrinder
On 9/4/2016 2:29 PM, Michał Brzuchalski wrote: >> Providing `mutator` | `mut` keyword as method modifier sounds liek a good >> idea, >> althought passing `$clone` parameter as first additional param could break >> method declaration and would be misleading. >> >> Assuming mutator method is designed

Re: [PHP-DEV] Non-conflicting PHP 5 and 7 builds

2016-09-04 Thread Davey Shafik
Jordan, This was a choice they made, yet the author of the Debian/Ubuntu packages has side-by-side installable versions from 5.5-7.1 in his own PPA: https://launchpad.net/~ondrej/+archive/ubuntu/php It's not only currently feasible, it has been done, the _project_ chose not to do it. - Davey O

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

2016-09-04 Thread Rowan Collins
On 04/09/2016 01:54, Davey Shafik wrote: No need to apologize, thank you for defending my idea and so eloquently — I will amend the RFC with your earlier suggestions; being as I will do so almost verbatim, would you mind being added as a co-author? I think it's a substantial contribution :) T

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

2016-09-04 Thread Rowan Collins
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

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

2016-09-04 Thread Tom Worster
On 9/2/16 3:32 PM, Davey Shafik wrote: Hi internals, I'd like to introduce a new RFC to deprecate pear/pecl (in 7.2, and remove in 8.0), Yes! It's good for the software (and its users) if it is maintained and contributed to using _currently_prevailing_conventions_ in f/oss. as well as ad

Re: [PHP-DEV] RFC - Immutable classes

2016-09-04 Thread Michał Brzuchalski
2016-09-04 14:10 GMT+02:00 Michał Brzuchalski : > > > 2016-09-04 10:55 GMT+02:00 Fleshgrinder : > >> Hi Chris! >> >> On 9/3/2016 5:00 PM, Chris Riley wrote: >> > - Properties can be declared immutable. Immutable properties may only be >> > changed under two circumstances: a) In the objects constru

Re: [PHP-DEV] RFC - Immutable classes

2016-09-04 Thread Michał Brzuchalski
2016-09-04 10:55 GMT+02:00 Fleshgrinder : > Hi Chris! > > On 9/3/2016 5:00 PM, Chris Riley wrote: > > - Properties can be declared immutable. Immutable properties may only be > > changed under two circumstances: a) In the objects constructor b) If they > > are null (This enables setter injection i

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

2016-09-04 Thread David Muir
> On 4 Sep 2016, at 6:48 PM, Lester Caine wrote: > >> On 03/09/16 22:53, Rowan Collins wrote: >> I guess we could have a philosophical debate about what it means for >> something to be "the standard" rather than "a standard", and whether >> PEAR was "more official" than PHP-FIG, and just who get

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

2016-09-04 Thread Niklas Keller
Tony Marston schrieb am So., 4. Sep. 2016, 10:38: > "Rowan Collins" wrote in message > news:b3bd7acf-a525-d921-1b1b-64ccf94b8...@gmail.com... > > > >On 02/09/2016 20:32, Davey Shafik wrote: > >> I'd like to introduce a new RFC to deprecate pear/pecl (in 7.2, and > >> remove > >> in 8.0), as well

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

2016-09-04 Thread Leigh
On Fri, 2 Sep 2016 at 20:33 Davey Shafik wrote: > > I believe that pickle solves the issues with regards to pecl, and have run > the idea passed Jordi and Pierre. Both are fine with this RFC. :) > > I understand that adding in composer/pickle is just setting us up for > having a future "Deprecate

Re: [PHP-DEV] RFC - Immutable classes

2016-09-04 Thread Fleshgrinder
Hi Chris! On 9/3/2016 5:00 PM, Chris Riley wrote: > - Properties can be declared immutable. Immutable properties may only be > changed under two circumstances: a) In the objects constructor b) If they > are null (This enables setter injection if required) > The constraint b) would make the object

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

2016-09-04 Thread Lester Caine
On 03/09/16 22:53, Rowan Collins wrote: > I guess we could have a philosophical debate about what it means for > something to be "the standard" rather than "a standard", and whether > PEAR was "more official" than PHP-FIG, and just who gets to decide what > PHP is. > > But once again, I find mysel

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

2016-09-04 Thread Tony Marston
"Rowan Collins" wrote in message news:b3bd7acf-a525-d921-1b1b-64ccf94b8...@gmail.com... On 02/09/2016 20:32, Davey Shafik wrote: I'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 plac

Re: [PHP-DEV] Non-conflicting PHP 5 and 7 builds

2016-09-04 Thread Jordan Gigov
I can see your argument for using prefix, but that would not provide a solution to package maintainers who may want to give their users a choice. I was recently surprised when upgrading from Ubuntu 14 to 16 that it replaced PHP 5 with 7 entirely. They were forced into choosing between the two at a