Re: [PHP-DEV] Modern practices ...

On 13/09/16 01:44, Pierre Joye wrote: > On Tue, Sep 13, 2016 at 3:06 AM, Lester Caine wrote: >> On 12/09/16 20:31, Christoph M. Becker wrote: >>> On 11.09.2016 at 12:35, Lester Caine wrote: >>> On 11/09/16 11:05, Christoph M. Becker wrote: >>> I have already debugged the problems and wil

Re: [PHP-DEV] Modern practices ...

On Tue, Sep 13, 2016 at 3:06 AM, Lester Caine wrote: > On 12/09/16 20:31, Christoph M. Becker wrote: >> On 11.09.2016 at 12:35, Lester Caine wrote: >> >>> On 11/09/16 11:05, Christoph M. Becker wrote: >> >>> I have already debugged the problems and will tidy up the notes later >>> when I cross che

Re: [PHP-DEV] Modern practices ...

On 12/09/16 20:31, Christoph M. Becker wrote: > On 11.09.2016 at 12:35, Lester Caine wrote: > >> On 11/09/16 11:05, Christoph M. Becker wrote: > >> I have already debugged the problems and will tidy up the notes later >> when I cross check things. This is the sort of support I've always >> provid

Re: [PHP-DEV] Modern practices ...

On 11.09.2016 at 12:35, Lester Caine wrote: > On 11/09/16 11:05, Christoph M. Becker wrote: > I have already debugged the problems and will tidy up the notes later > when I cross check things. This is the sort of support I've always > provided to the PHP project. The pages relating to the compile

Re: [PHP-DEV] Modern practices ...

On 11/09/16 11:05, Christoph M. Becker wrote: > On 10.09.2016 at 23:45, Lester Caine wrote: > >> On 10/09/16 16:41, Christoph M. Becker wrote: >> >>> Despite the rather common myth, building PHP on Windows nowadays is not >>> really harder than on Linux. Detailed instructions are available on >>>

Re: [PHP-DEV] Modern practices ...

On 10.09.2016 at 23:45, Lester Caine wrote: > On 10/09/16 16:41, Christoph M. Becker wrote: > >> Despite the rather common myth, building PHP on Windows nowadays is not >> really harder than on Linux. Detailed instructions are available on >>

Re: [PHP-DEV] Modern practices ...

On 11/09/16 07:06, Pierre Joye wrote: > On Sep 10, 2016 3:32 PM, "Lester Caine" wrote: > >> I think I am right in saying Pierre originally needed pickle so that >> PEAR could be dropped in the windows? > > It was not the reason. > > My main motivation is about ease developer work (no informatio

Re: [PHP-DEV] Modern practices ...

On Sep 10, 2016 3:32 PM, "Lester Caine" wrote: > I think I am right in saying Pierre originally needed pickle so that > PEAR could be dropped in the windows? It was not the reason. My main motivation is about ease developer work (no information duplication, wrong version number, binary support

Re: [PHP-DEV] Modern practices ...

On 10/09/16 16:41, Christoph M. Becker wrote: > Despite the rather common myth, building PHP on Windows nowadays is not > really harder than on Linux. Detailed instructions are available on > . http://lsces.co.uk/wiki/Compile+PHP7+Build+on+W

Re: [PHP-DEV] Modern practices ...

On 10.09.2016 at 17:09, Lester Caine wrote: > On 10/09/16 09:32, Lester Caine wrote: > >> Doing some digging I've found the conversations on this back in 2011. At >> that time the statement was made that 'php project does not provide >> binary builds' and 'if the user can't install a compiler they

Re: [PHP-DEV] Modern practices ...

On 10/09/16 09:32, Lester Caine wrote: > Doing some digging I've found the conversations on this back in 2011. At > that time the statement was made that 'php project does not provide > binary builds' and 'if the user can't install a compiler they should not > be using php'. I'll not name the sourc

Re: [PHP-DEV] Modern practices ...

On Sat, Sep 10, 2016 at 10:32 AM, Lester Caine wrote: > On 09/09/16 14:28, Lester Caine wrote: > > I'd forgotten the official windows packages no longer had PEAR anyway. > > Does make the discussion on that somewhat academic? We have been > > installing Linux servers as replacements to the window

Re: [PHP-DEV] Modern practices ...

On 09/09/16 14:28, Lester Caine wrote: > I'd forgotten the official windows packages no longer had PEAR anyway. > Does make the discussion on that somewhat academic? We have been > installing Linux servers as replacements to the windows boxes so the > need to actually load newer windows builds as b

Re: [PHP-DEV] Modern practices ...

On 09/09/16 13:32, Ferenc Kovacs wrote: > On Fri, Sep 9, 2016 at 1:45 PM, Lester Caine wrote: > >> > On 09/09/16 12:35, Ferenc Kovacs wrote: >>> > > but please, this is really offtopic on this list. >> > >> > See my other reply ... >> > and composer global mode as provided out of the box is NOT a

Re: [PHP-DEV] Modern practices ...

Hello, For myself I have adopted the "vagrant vm per project" workflow. I never mix projects, because while some are "primitive" and do not require anything beyond a standard install, others have a custom provisioning and setup stuff. And specific options on the software that can interfere with o

Re: [PHP-DEV] Modern practices ...

On Fri, Sep 9, 2016 at 1:45 PM, Lester Caine wrote: > On 09/09/16 12:35, Ferenc Kovacs wrote: > > but please, this is really offtopic on this list. > > See my other reply ... > and composer global mode as provided out of the box is NOT an > alternative to installing the sort of production and dev

Re: [PHP-DEV] Modern practices ...

On 09/09/16 12:35, Ferenc Kovacs wrote: > but please, this is really offtopic on this list. See my other reply ... and composer global mode as provided out of the box is NOT an alternative to installing the sort of production and development - command line - tools that PEAR currently manages happi

Re: [PHP-DEV] Modern practices ...

On Fri, Sep 9, 2016 at 1:00 PM, Lester Caine wrote: > On 09/09/16 11:30, Niklas Keller wrote: > >> Back to PEAR ... what happens if I simply install a copy of composer > >> > centrally and rename it 'PEAR'. > > > > Why rename it to PEAR? It's a different tool. Just call it Composer as > it's > >

Re: [PHP-DEV] Modern practices ...

On 09/09/16 11:55, Ferenc Kovacs wrote: >> Most sites will skip whole major versions of updates simply >> becuase their production system IS working ... > > usually it is easier to migrate in multiple smaller steps, but of course > there are people who will do the one big upgrade. Many of the si

Re: [PHP-DEV] Modern practices ...

On 09/09/16 11:30, Niklas Keller wrote: >> Back to PEAR ... what happens if I simply install a copy of composer >> > centrally and rename it 'PEAR'. > > Why rename it to PEAR? It's a different tool. Just call it Composer as it's > named. My point was just that as has already been established. com

Re: [PHP-DEV] Modern practices ...

On Fri, Sep 9, 2016 at 10:39 AM, Lester Caine wrote: > Having slept on the discussion about people today expecting users each > to have their own environment, I came to the something of an impasse. > How many Linux installations run a package manager that allows > individual users to install thei

Re: [PHP-DEV] Modern practices ...

On 9 September 2016 09:39:07 BST, Lester Caine wrote: >Back to PEAR ... what happens if I simply install a copy of composer >centrally and rename it 'PEAR'. composer.phar simply gets installed >centrally and any new tech has access without having to install their >own copy. This is more or less

Re: [PHP-DEV] Modern practices ...

2016-09-09 10:39 GMT+02:00 Lester Caine : > Having slept on the discussion about people today expecting users each > to have their own environment, I came to the something of an impasse. > How many Linux installations run a package manager that allows > individual users to install their own versio

[PHP-DEV] Modern practices ...

Having slept on the discussion about people today expecting users each to have their own environment, I came to the something of an impasse. How many Linux installations run a package manager that allows individual users to install their own versions of Apache/PHP/Database/Git/Hg and so on. The who