;Cc: Sherif Ramadan ; Stanislav Malyshev ; internals@lists.php.net
> >Subject: Re: [PHP-DEV] [RFC] Deprecate PEAR/PECL & Replace with
> composer/pickle
> >
> >On Mon, Sep 12, 2016 at 9:32 AM, Tony Marston
> wrote:
> >
> >Sent: Sunday, September 11, 2016 11:44 AM
>
On Mon, 12 Sep 2016, Niklas Keller wrote:
> 2016-09-12 10:21 GMT+02:00 Derick Rethans :
>
> > On Mon, 12 Sep 2016, Pierre Joye wrote:
> >
> > > This RFC is about stop bundling it with the php releases and propose
> > > composer/pickle instead. Everything else has nothing to do with this
> > > RFC
Sent: Monday, September 12, 2016 12:34 PM
>To: Tony Marston
>Cc: Sherif Ramadan ; Stanislav Malyshev ; internals@lists.php.net
>Subject: Re: [PHP-DEV] [RFC] Deprecate PEAR/PECL & Replace with composer/pickle
>
>On Mon, Sep 12, 2016 at 9:32 AM, Tony Marston wrote:
>
>S
>
> It is NOT insulting to say that people who still insist on using command
> line tools are living in the past for the simple reason that the command
> line interface was replaced with the GUI when the Windows OS was released
> in the 1990s. That is 25 years ago. Is that in the past or what? With
On Mon, Sep 12, 2016 at 1:51 PM, Nikita Popov wrote:
> On Mon, Sep 12, 2016 at 1:42 PM, Ferenc Kovacs wrote:
>
>> On Mon, Sep 12, 2016 at 10:21 AM, Derick Rethans wrote:
>>
>> > On Mon, 12 Sep 2016, Pierre Joye wrote:
>> >
>> > > This RFC is about stop bundling it with the php releases and prop
On Sep 12, 2016 6:51 PM, "Nikita Popov" wrote:
>
> On Mon, Sep 12, 2016 at 1:42 PM, Ferenc Kovacs wrote:
>>
>> On Mon, Sep 12, 2016 at 10:21 AM, Derick Rethans wrote:
>>
>> > On Mon, 12 Sep 2016, Pierre Joye wrote:
>> >
>> > > This RFC is about stop bundling it with the php releases and propose
On Mon, Sep 12, 2016 at 1:42 PM, Ferenc Kovacs wrote:
> On Mon, Sep 12, 2016 at 10:21 AM, Derick Rethans wrote:
>
> > On Mon, 12 Sep 2016, Pierre Joye wrote:
> >
> > > This RFC is about stop bundling it with the php releases and propose
> > > composer/pickle instead. Everything else has nothing
On Mon, Sep 12, 2016 at 10:21 AM, Derick Rethans wrote:
> On Mon, 12 Sep 2016, Pierre Joye wrote:
>
> > This RFC is about stop bundling it with the php releases and propose
> > composer/pickle instead. Everything else has nothing to do with this
> > RFC (aka web frontend, what happens or not on p
On Sep 12, 2016 3:24 PM, "Stanislav Malyshev" wrote:
>
> Hi!
>
> >> PEAR/PECL as a package manager has historically had little utility to
the
> >> average user apart from installing those PECL extensions which aren't
> >> packaged by a particular user's distribution repository. Certainly
hasn't
>
On Mon, Sep 12, 2016 at 10:24 AM, Stanislav Malyshev
wrote:
> Hi!
>
> >> PEAR/PECL as a package manager has historically had little utility to
> the
> >> average user apart from installing those PECL extensions which aren't
> >> packaged by a particular user's distribution repository. Certainly
>
On Mon, Sep 12, 2016 at 9:32 AM, Tony Marston
wrote:
> Sent: Sunday, September 11, 2016 11:44 AM
> >To: Tony Marston
> >Cc: Stanislav Malyshev ; internals@lists.php.net
> >Subject: Re: [PHP-DEV] [RFC] Deprecate PEAR/PECL & Replace with
> composer/pickle
> >
2016-09-12 10:21 GMT+02:00 Derick Rethans :
> On Mon, 12 Sep 2016, Pierre Joye wrote:
>
> > This RFC is about stop bundling it with the php releases and propose
> > composer/pickle instead. Everything else has nothing to do with this
> > RFC (aka web frontend, what happens or not on pear.php.net,
Hi!
> It's curious to see though that the off-topic comments get replies, but
> few real concerns do from the RFC author - such as not removing
> something before we have a confirmed alternative. I'd like to trial
> pickle first for a few releases and only then see whether to remove the
> PEAR
I think Derick has a good point here. I agree on the part that we should
stop bundling PEAR/PECL, but we might be rushing into pickle too fast.
2016-09-12 10:21 GMT+02:00 Derick Rethans :
> On Mon, 12 Sep 2016, Pierre Joye wrote:
>
> > This RFC is about stop bundling it with the php releases and
Hi!
>> PEAR/PECL as a package manager has historically had little utility to the
>> average user apart from installing those PECL extensions which aren't
>> packaged by a particular user's distribution repository. Certainly hasn't
>> had any real viability in years. Trying to replace something tha
On Mon, 12 Sep 2016, Pierre Joye wrote:
> This RFC is about stop bundling it with the php releases and propose
> composer/pickle instead. Everything else has nothing to do with this
> RFC (aka web frontend, what happens or not on pear.php.net, its
> packages, etc.).
>
> To all: please re focus
On Sun, 11 Sep 2016, Sherif Ramadan wrote:
> On Sun, Sep 11, 2016 at 4:47 AM, Tony Marston
> PEAR/PECL as a package manager has historically had little utility to the
> average user apart from installing those PECL extensions which aren't
> packaged by a particular user's distribution repository.
On Sep 12, 2016 2:36 PM, "Tony Marston" wrote:
>
> Sent: Sunday, September 11, 2016 8:32 PM
> >To: Tony Marston ; Stanislav Malyshev ; internals@lists.php.net
> >Subject: Re: [PHP-DEV] [RFC] Deprecate PEAR/PECL & Replace with
composer/pickle
> >
> >
&
Sent: Sunday, September 11, 2016 8:32 PM
>To: Tony Marston ; Stanislav Malyshev ; internals@lists.php.net
>Subject: Re: [PHP-DEV] [RFC] Deprecate PEAR/PECL & Replace with composer/pickle
>
>
>On 09/11/2016 10:47 AM, Tony Marston wrote:
>> Sent: Saturday, September 10,
Sent: Sunday, September 11, 2016 11:44 AM
>To: Tony Marston
>Cc: Stanislav Malyshev ; internals@lists.php.net
>Subject: Re: [PHP-DEV] [RFC] Deprecate PEAR/PECL & Replace with composer/pickle
>
>On Sun, Sep 11, 2016 at 4:47 AM, Tony Marston wrote:
>
>Sent: Saturday, Septem
On 09/11/2016 10:47 AM, Tony Marston wrote:
> Sent: Saturday, September 10, 2016 7:47 PM
>> To: Tony Marston ; internals@lists.php.net
>> Subject: Re: [PHP-DEV] [RFC] Deprecate PEAR/PECL & Replace with
>> composer/pickle
>> Hi!
>>
>>> You seem to t
On 11/09/16 11:44, Sherif Ramadan wrote:
> I just want to say that PEAR as a source repository, has been dead for
> quite some time. It's filled with outdated code that has hardly seen any
> maintenance in years, and nobody really contributes to it anyway.
While I will agree that for a large secti
On Sun, Sep 11, 2016 at 4:47 AM, Tony Marston
wrote:
> Sent: Saturday, September 10, 2016 7:47 PM
> >To: Tony Marston ; internals@lists.php.net
> >Subject: Re: [PHP-DEV] [RFC] Deprecate PEAR/PECL & Replace with
> composer/pickle
>
>
> Then I suggest that those who
Sent: Saturday, September 10, 2016 7:47 PM
>To: Tony Marston ; internals@lists.php.net
>Subject: Re: [PHP-DEV] [RFC] Deprecate PEAR/PECL & Replace with composer/pickle
>Hi!
>
>> You seem to think that any opinion which differs from yours is wrong,
>> and you try to dism
Sent: Friday, September 09, 2016 10:08 AM
>To: Tony Marston
>Cc: PHP Internals
>Subject: Re: [PHP-DEV] [RFC] Deprecate PEAR/PECL & Replace with composer/pickle
>
>2016. szept. 9. 10:44 ezt írta ("Tony Marston" ):
>>
>> Sent: Thursday, September 08, 2016
On 11 Sep 2016 10:04 am, "Lester Caine" wrote:
>
> On 10/09/16 19:47, Stanislav Malyshev wrote:
> > In fact, Windows does have command-line interface, moreover - Microsoft
> > recently invested significant resources into making this interface more
> > powerful and flexible. Moreover, many of the p
On 10/09/16 19:47, Stanislav Malyshev wrote:
> In fact, Windows does have command-line interface, moreover - Microsoft
> recently invested significant resources into making this interface more
> powerful and flexible. Moreover, many of the professional programmers
> routinely use command-line tools
Hi!
> You seem to think that any opinion which differs from yours is wrong,
> and you try to dismiss that opinion by classing it as "abusive". I'm
> afraid this lack of tolerance for different opinions is becoming more
> and more prevalent in this forum, and I fear it will have a detrimental
> eff
On Sep 10, 2016 4:19 PM, "Tony Marston" wrote:
> That is a valid opinion. Consider the fact that the Windows operating
system was only accepted by large numbers of users as it had a "modern" GUI
and not a command line interface. You try and release a new piece of
software to users that does not h
"Ferenc Kovacs" wrote in message
news:CAH-PCH5gu6Fz2wQU+n0J7MEGj9=wqR_UmxOd1BhQWriJ=2j...@mail.gmail.com...
2016. szept. 9. 10:44 ezt írta ("Tony Marston" ):
Sent: Thursday, September 08, 2016 9:35 AM
>To: Tony Marston
>Cc: PHP Internals
>Subject: Re: [PHP-D
On 09/09/2016 11:01, Tony Marston wrote:
Sent: Friday, September 09, 2016 12:55 AM
To: Tony Marston ; internals@lists.php.net
Subject: Re: [PHP-DEV] [RFC] Deprecate PEAR/PECL & Replace with composer/pickle
Hi!
There should be a rule that nothing can be deprecated unless there is a
vi
2016. szept. 9. 10:44 ezt írta ("Tony Marston" ):
>
> Sent: Thursday, September 08, 2016 9:35 AM
> >To: Tony Marston
> >Cc: PHP Internals
> >Subject: Re: [PHP-DEV] [RFC] Deprecate PEAR/PECL & Replace with
composer/pickle
> >
> >
>
Sent: Friday, September 09, 2016 12:55 AM
>To: Tony Marston ; internals@lists.php.net
>Subject: Re: [PHP-DEV] [RFC] Deprecate PEAR/PECL & Replace with composer/pickle
>Hi!
>
>> There should be a rule that nothing can be deprecated unless there is a
>> viable, stable,
Sent: Thursday, September 08, 2016 1:44 PM
>To: Tony Marston
>Cc: PHP internals
>Subject: Re: [PHP-DEV] [RFC] Deprecate PEAR/PECL & Replace with composer/pickle
>
>On Sep 8, 2016 3:05 PM, "Tony Marston" wrote:
>>
>> "Pierre Joye&quo
Sent: Thursday, September 08, 2016 9:15 AM
>To: Tony Marston
>Cc: PHP Internals
>Subject: Re: [PHP-DEV] [RFC] Deprecate PEAR/PECL & Replace with composer/pickle
>
>
>On Thu, Sep 8, 2016 at 9:43 AM, Tony Marston wrote:
>
>"Ferenc Kov
Hi!
> There should be a rule that nothing can be deprecated unless there is a
> viable, stable, fully functioning and fully supported alternative. I do
> not like the way that some people simply say "I do not like this. I do
> not use this. Nobody should be using this. Let's deprecate it"
You can
On Thu, Sep 8, 2016 at 1:34 AM, Michael Morris wrote:
> On Thu, Sep 8, 2016 at 4:27 AM, Daniel Morris
> wrote:
>
> > On Thu, 8 Sep 2016, at 08:43 AM, Tony Marston wrote:
> > > Perhaps users could be prevented from making such basic mistakes if
> they
> > > had
> > > a 21st century web interface
On Sep 8, 2016 3:05 PM, "Tony Marston" wrote:
>
> "Pierre Joye" wrote in message
news:caezptu4twuap1xjx+z_n+sgj1ujptyn8pj5xuvmjei2dke0...@mail.gmail.com...
>
>>
>> hi Tony,
>>
>> On Wed, Sep 7, 2016 at 2:52 PM, Tony Marston
wrote:
>>>
>>> "Pierre Joye" wrote in message
>>> news:CAEZPtU6aHYb9HsN
On Thu, 8 Sep 2016, at 11:35 AM, Lester Caine wrote:
> I know this is a problem for PHP_CodeSniffer to rework it's
> documentation, but it is a chicken and egg. PEAR provides a framework to
> store things like PHP_CodeSniffer in the common area away from our web
> folders. A similar set of guidelin
On Wed, 7 Sep 2016, Michael Wallner wrote:
> +1 on stabbing the PEAR installer from the source distribution.
The PEAR installer is not just the *PEAR* installer, it
installs and packages PECL extensions too. Actually, it's the only way
how people directly install PECL extensions.
> -1 on addi
On 08/09/16 09:24, Daniel Morris wrote:
> On Thu, 8 Sep 2016, at 09:07 AM, Lester Caine wrote:
>> I've just been through an exercise to give PHP_CodeSniffer a go on my
>> code base. I've not worried too much about that in the past since
>> Eclipse in general flags style problems as well as simple e
On Thu, Sep 8, 2016 at 9:49 AM, Tony Marston
wrote:
> "Michael Morris" wrote in message news:CAEUnE0dfjJ02g2Rhkp9WvnkS
> XpoLzjK=tmivdbsucccgxw2...@mail.gmail.com...
>
>
>> On Wed, Sep 7, 2016 at 3:52 AM, Tony Marston
>> wrote:
>>
>>>
>>>
>>> Typical. You create a useful tool, get your users ho
On Thu, Sep 8, 2016 at 4:27 AM, Daniel Morris
wrote:
> On Thu, 8 Sep 2016, at 08:43 AM, Tony Marston wrote:
> > Perhaps users could be prevented from making such basic mistakes if they
> > had
> > a 21st century web interface instead of the archaic command line.
>
> Why don't you make one?
>
>
Be
On 08/09/2016 10:05, Tony Marston wrote:
"Pierre Joye" wrote in message
news:caezptu4twuap1xjx+z_n+sgj1ujptyn8pj5xuvmjei2dke0...@mail.gmail.com...
hi Tony,
On Wed, Sep 7, 2016 at 2:52 PM, Tony Marston
wrote:
"Pierre Joye" wrote in message
news:CAEZPtU6aHYb9HsNXbXWp9q9PMoLYiJp=n1rjmspofm
On 08/09/2016 09:05, Tony Marston wrote:
I had to debug and fix every error myself, but now I have the PEAR web
interface up and running.
Have you contributed these patches back to the community for others to
benefit from? Perhaps you could adopt the maintainerless package yourself?
There a
On Thu, 8 Sep 2016, at 08:43 AM, Tony Marston wrote:
> Perhaps users could be prevented from making such basic mistakes if they
> had
> a 21st century web interface instead of the archaic command line.
Why don't you make one?
--
Daniel Morris
dan...@honestempire.com
--
PHP Internals - PHP Runt
On Thu, 8 Sep 2016, at 09:07 AM, Lester Caine wrote:
> I've just been through an exercise to give PHP_CodeSniffer a go on my
> code base. I've not worried too much about that in the past since
> Eclipse in general flags style problems as well as simple errors. This
> is a package that SUSE does not
On Thu, Sep 8, 2016 at 9:43 AM, Tony Marston
wrote:
> "Ferenc Kovacs" wrote in message news:CAH-PCH568TPsztkWT553QVQy
> 7jsp1tcqt5w+ot1pocdt-pb...@mail.gmail.com...
>
>>
>> On Wed, Sep 7, 2016 at 9:49 AM, Tony Marston
>> wrote:
>>
>> "Ferenc Kovacs" wrote in message news:CAH-PCH5qHdYen33Q_s7kT
On 02/09/16 20:32, Davey Shafik wrote:
> I'm also proposing voting choices around the optional/default introduction
> of composer/pickle.
I've just been through an exercise to give PHP_CodeSniffer a go on my
code base. I've not worried too much about that in the past since
Eclipse in general flags
"Pierre Joye" wrote in message
news:caezptu4twuap1xjx+z_n+sgj1ujptyn8pj5xuvmjei2dke0...@mail.gmail.com...
hi Tony,
On Wed, Sep 7, 2016 at 2:52 PM, Tony Marston
wrote:
"Pierre Joye" wrote in message
news:CAEZPtU6aHYb9HsNXbXWp9q9PMoLYiJp=n1rjmspofmhbebd...@mail.gmail.com...
Happy to see
"Michael Morris" wrote in message
news:CAEUnE0dfjJ02g2Rhkp9WvnkSXpoLzjK=tmivdbsucccgxw2...@mail.gmail.com...
On Wed, Sep 7, 2016 at 3:52 AM, Tony Marston
wrote:
Typical. You create a useful tool, get your users hooked, then walk away
and leave them dangling.
No one owes you anything. You
"Ferenc Kovacs" wrote in message
news:cah-pch568tpsztkwt553qvqy7jsp1tcqt5w+ot1pocdt-pb...@mail.gmail.com...
On Wed, Sep 7, 2016 at 9:49 AM, Tony Marston
wrote:
"Ferenc Kovacs" wrote in message news:CAH-PCH5qHdYen33Q_s7kTKM_
8qk71v8ky6kt4fzurfawfx0...@mail.gmail.com...
Composer doesn't
Hi Davey,
thanks for the proposal and excuse my rather longish reply already.
> On 02 Sep 2016, at 21: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
Regards,
Mike
> On 02 09 2016, at 21:32, 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 their place.
>
> https://wiki.php.net/rfc/deprecate
On Friday, September 2, 2016, 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 their place.
>
> https://wiki.php.net/rfc/deprecate-pear-include-compo
On Sep 7, 2016 6:24 PM, "Lester Caine" wrote:
>
> On 07/09/16 12:02, Pierre Joye wrote:
> > One point, pickle does not need composer to run.
> >
> > pickle install memcache will install the memcache extension (windows
> > binaries, from pecl.php.net, etc) straight away.
>
> That one is useful to
On 07/09/16 12:37, Rowan Collins wrote:
> On 07/09/2016 11:51, Lester Caine wrote:
>> This comes down simply to 'education', and just as we provide migration
>> guides to check deprecated code and help re-write it there needs to be
>> the same sort of guideline - provided by PHP - as to how compose
On 07/09/2016 11:51, Lester Caine wrote:
This comes down simply to 'education', and just as we provide migration
guides to check deprecated code and help re-write it there needs to be
the same sort of guideline - provided by PHP - as to how composer or
what ever can be used to replace the previou
On 07/09/16 12:02, Pierre Joye wrote:
> One point, pickle does not need composer to run.
>
> pickle install memcache will install the memcache extension (windows
> binaries, from pecl.php.net, etc) straight away.
That one is useful to know. I have all my own active pear stuff under
the code repo
On Wed, Sep 7, 2016 at 5:51 PM, Lester Caine wrote:
> On 07/09/16 10:58, Rowan Collins wrote:
> People who already know composer, as perhaps it's all they have ever
> used, are at an advantage. I've tried a couple of times to pick up a
> library that NOW has a composer option, Smarty is a case in
On 07/09/16 10:58, Rowan Collins wrote:
>
> If anything, the Composer approach is simpler to deploy, because you can
> create a tar ball of the whole project with a populated vendor
> directory, and copy it straight to production. (I believe that's
> possible with PEAR, too, but not when using the
On 07/09/2016 10:33, Lester Caine wrote:
This does highlight the different approach to handling things in a
production environment over a development one. The problems I have seen
IS when composer.lock gets replaced by mistake, or when an update picks
up a change to a package that was not actuall
On 07/09/2016 11:33, Lester Caine wrote:
On 07/09/16 09:10, Ferenc Kovacs wrote:
I can only report what I have read in various newsgroups and forums, and
they have said that composer has screwed up their installations. If it is
capable of doing that then it is a serious issue that needs addre
2016-09-07 11:33 GMT+02:00 Lester Caine :
> On 07/09/16 09:10, Ferenc Kovacs wrote:
> >> I can only report what I have read in various newsgroups and forums, and
> >> > they have said that composer has screwed up their installations. If
> it is
> >> > capable of doing that then it is a serious iss
On 07/09/16 09:10, Ferenc Kovacs wrote:
>> I can only report what I have read in various newsgroups and forums, and
>> > they have said that composer has screwed up their installations. If it is
>> > capable of doing that then it is a serious issue that needs addressing.
>
> you can, but you shoul
hi Tony,
On Wed, Sep 7, 2016 at 2:52 PM, Tony Marston wrote:
> "Pierre Joye" wrote in message
> news:CAEZPtU6aHYb9HsNXbXWp9q9PMoLYiJp=n1rjmspofmhbebd...@mail.gmail.com...
>
>> Happy to see there are still users for this tool, Christian and I had
>> good fun writing it. Also you should know that
On Wed, Sep 7, 2016 at 3:52 AM, Tony Marston
wrote:
>
>
> Typical. You create a useful tool, get your users hooked, then walk away
> and leave them dangling.
>
>
No one owes you anything. You aren't entitled to get free updates to a free
tool. If the author wants to move onto other projects, that'
On Wed, Sep 7, 2016 at 9:49 AM, Tony Marston
wrote:
> "Ferenc Kovacs" wrote in message news:CAH-PCH5qHdYen33Q_s7kTKM_
> 8qk71v8ky6kt4fzurfawfx0...@mail.gmail.com...
>
>>
>>
>>>
>>> Composer doesn't do that.
>>> Then how come I've seen several complaints in various forums about
>>> comp
"Pierre Joye" wrote in message
news:CAEZPtU6aHYb9HsNXbXWp9q9PMoLYiJp=n1rjmspofmhbebd...@mail.gmail.com...
Hi Tony,
On Tue, Sep 6, 2016 at 2:17 PM, Tony Marston
wrote:
"Niklas Keller" wrote in message
news:canuqdcjeh45_2aeq74cceoy4xc3xj0o_+yrq2nvy0k2vdox...@mail.gmail.com...
Tony Marston
"Ferenc Kovacs" wrote in message
news:cah-pch5qhdyen33q_s7ktkm_8qk71v8ky6kt4fzurfawfx0...@mail.gmail.com...
Composer doesn't do that.
Then how come I've seen several complaints in various forums about
composer updating libraries in the background and screwing things up.
That proves no
On 5/09/2016 8:13 PM, Derick Rethans wrote:
On Fri, 2 Sep 2016, 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 place.
https://wiki.php.net/rfc/deprecate-pear-in
On Fri, Sep 2, 2016 at 8: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), as well as add composer/pickle (optional in 7.2, default in 7.3+)
> in their place.
Can pickle package the extension? That's basically th
On Sep 6, 2016 6:29 PM, "Ferenc Kovacs" wrote:
>
> On Tue, Sep 6, 2016 at 12:40 PM, Rowan Collins
> wrote:
>
> > On 06/09/2016 11:18, Derick Rethans wrote:
> >
> >> One of PHPs biggest strengths is the availability of an extension for
> >> nearly everything. There are *1000s* out there. Some made
On Tue, Sep 6, 2016 at 12:40 PM, Rowan Collins
wrote:
> On 06/09/2016 11:18, Derick Rethans wrote:
>
>> One of PHPs biggest strengths is the availability of an extension for
>> nearly everything. There are *1000s* out there. Some made by single
>> people, some by small groups of people, or some b
Hi Tony,
On Tue, Sep 6, 2016 at 2:17 PM, Tony Marston wrote:
> "Niklas Keller" wrote in message
> news:canuqdcjeh45_2aeq74cceoy4xc3xj0o_+yrq2nvy0k2vdox...@mail.gmail.com...
>
>>
>> Tony Marston schrieb am So., 4. Sep. 2016,
>> 10:38:
>>
>>> "Rowan Collins" wrote in message
>>> news:b3bd7acf-a5
On 06/09/2016 11:18, Derick Rethans wrote:
One of PHPs biggest strengths is the availability of an extension for
nearly everything. There are *1000s* out there. Some made by single
people, some by small groups of people, or some by large companies. You
can't expect *all* of these extensions to be
On Tue, 6 Sep 2016, Sebastian Bergmann wrote:
> Am 05.09.2016 um 12:13 schrieb Derick Rethans:
> > You can't really ship PHP without a way to install extensions though!
>
> Why not?
>
> IMHO, PHP should not be shipped with any tool for installing PHP
> components (PEAR Installer, Composer, ...)
On Mon, 5 Sep 2016, Davey Shafik wrote:
> Nobody is saying to do anything except unbundle the command line tools.
And I would say that we should see whether the new tools work
perfectly fine first before even considering that.
cheers,
Derick
--
PHP Internals - PHP Runtime Development Mailing
>
>
>> Composer doesn't do that.
>>
>
> Then how come I've seen several complaints in various forums about
> composer updating libraries in the background and screwing things up.
> That proves nothing except that your knowledge is very limited.
indeed it does.
--
Ferenc Kovács
@Tyr43l - ht
Hi,
On 09/06/2016 09:14 AM, Sebastian Bergmann wrote:
Am 05.09.2016 um 12:13 schrieb Derick Rethans:
You can't really ship PHP without a way to install extensions though!
Why not?
IMHO, PHP should not be shipped with any tool for installing PHP
components (PEAR Installer, Composer, ...) or e
On 6 September 2016 08:17:20 BST, Tony Marston wrote:
>>I do NOT want the replacement PEAR library to update itself in the
>>> background.
>>
>>Composer doesn't do that.
>
>Then how come I've seen several complaints in various forums about
>composer
>updating libraries in the background and screw
On 6 September 2016 08:06:09 BST, Tony Marston wrote:
>The package name is PEAR_Frontend_Web. It is documented at
>http://pear.php.net/reference/PEAR_Frontend_Web-latest/
Thanks, if that's bundled with PHP (i.e. you don't need to run "pear install
PEAR_Frontend_Web" to find it) then that should
"Niklas Keller" wrote in message
news:canuqdcjeh45_2aeq74cceoy4xc3xj0o_+yrq2nvy0k2vdox...@mail.gmail.com...
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:
>
Am 05.09.2016 um 12:13 schrieb Derick Rethans:
> You can't really ship PHP without a way to install extensions though!
Why not?
IMHO, PHP should not be shipped with any tool for installing PHP
components (PEAR Installer, Composer, ...) or extensions (PECL Installer,
...).
In my experience, peop
Hi!
> Just because SOME people still like using a command line interface does
> not mean that they can force everyone else to use it. If any piece of
Nobody is forcing you to use anything.
> 21st century does not come with a web/GUI interface it just shows that
> the author is still living in th
"Rowan Collins" wrote in message
news:be378f46-9a69-55e5-7e2f-48dfbfd8b...@gmail.com...
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 EXCL
"Stanislav Malyshev" wrote in message
news:1aad32b9-8481-2fb4-4912-66705bd59...@gmail.com...
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 unaccept
On 05/09/16 19:51, Davey Shafik wrote:
> https://github.com/dshafik/php7-mysql-shim — I already solved that problem,
> at least in the short term.
Another one for PHPSurgery MUST get that updated ... when time permits.
--
Lester Caine - G8HFL
-
Contact - http://lsces.
On Mon, Sep 5, 2016 at 8:31 AM, Michael Morris wrote:
> Please be cautious - composer isn't a complete replacement for PEAR
> because it doesn't behave the same way. For the most part this is a good
> thing, but please consider the following.
>
> On not one but two occasions I was tasked after be
On Mon, Sep 5, 2016 at 8:57 AM, Lester Caine wrote:
> On 05/09/16 16:31, Michael Morris wrote:
> > Also, as Tony Marston pointed out, there are CPanel systems that allow
> the
> > pear libraries to be managed from a web gui. Given time I'm sure the
> folks
> > at cpanel will build new interfaces
On 05/09/2016 11:13, Derick Rethans wrote:
And it should work also work out of the box, without any other tricks or
steps to make it working. That means, not having to run "composer
install" in order to get a working "pickle" tool. A phar might be an
idea.
As I understand, PEAR already needs so
On 05/09/2016 16:31, Michael Morris wrote:
Also, as Tony Marston pointed out, there are CPanel systems that allow the
pear libraries to be managed from a web gui.
On 05/09/2016 16:57, Lester Caine wrote:
So this is not about 'Deprecate' the
code, but just the loader bit?
Have a look at my po
On 05/09/2016 11:12, Michał Brzuchalski wrote:
I think the idea involved from other languages package managers like nodejs
I think you have your history in a twist there: node.js was first
released in 2009, by which time PEAR was already ten years old, and
heading towards decline.
The more
On 05/09/16 16:31, Michael Morris wrote:
> Also, as Tony Marston pointed out, there are CPanel systems that allow the
> pear libraries to be managed from a web gui. Given time I'm sure the folks
> at cpanel will build new interfaces for new systems if it's possible.
> Composer however doesn't real
2016. szept. 5. 17:32 ezt írta ("Michael Morris" ):
>
> Please be cautious - composer isn't a complete replacement for PEAR
because
> it doesn't behave the same way. For the most part this is a good thing,
but
> please consider the following.
>
> On not one but two occasions I was tasked after bein
Please be cautious - composer isn't a complete replacement for PEAR because
it doesn't behave the same way. For the most part this is a good thing, but
please consider the following.
On not one but two occasions I was tasked after being hired with upgrading
PHP versions from 4.x to 5.3. In both c
Hi Tyrael
On Sep 5, 2016 7:10 AM, "Ferenc Kovacs" wrote:
>
> You are probably talking about https://bugs.php.net/bug.php?id=71224.
>
> My understanding is that when fetching the packages from pecl.php.net
> pickle would still have the same problem (
> https://github.com/FriendsOfPHP/pickle/issue
On Fri, 2 Sep 2016, 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 place.
>
> https://wiki.php.net/rfc/deprecate-pear-include-composer
>
> I highly recommen
2016-09-05 11:51 GMT+02:00 Dan Ackroyd :
> On 2 September 2016 at 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 place.
>
> Even if Pear and P
On 2 September 2016 at 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 place.
Even if Pear and Pecl overlap and share code, it would be better to
focus o
1 - 100 of 131 matches
Mail list logo
