Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:95860
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.47 as permitted sender)
MIME-Version: 1.0
References: <616bb9ff-bcd1-fd70-b251-05b280b5003e@lsces.co.uk>
 <CANUQDCh=xC5G2FS2a-jm3aKATwV1BuOhd+AQiCq7tnMUvruFcA@mail.gmail.com>
 <fc0df908-0e9d-e748-70cb-9d9a6e8d4ee6@lsces.co.uk> <CAH-PCH5FadFFygmXQE35Fzr6sDniG8rdsnVvWA9FYE+404RYog@mail.gmail.com>
 <e441c74d-7c4a-393a-fa05-21b9f80fd214@lsces.co.uk> <CAH-PCH6vE4EV0YaX-q_USUdH1KcsemMhbvN=e9iKqCpEPnrHfw@mail.gmail.com>
In-Reply-To: <CAH-PCH6vE4EV0YaX-q_USUdH1KcsemMhbvN=e9iKqCpEPnrHfw@mail.gmail.com>
Date: Fri, 09 Sep 2016 13:20:37 +0000
Message-ID: <CAL0xaBHv+DnLy+RoGPSCgL6hQ1GQVxiqG75as5DgxpedYAMS+A@mail.gmail.com>
To: Ferenc Kovacs <tyra3l@gmail.com>, Lester Caine <lester@lsces.co.uk>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11442bb4aec45b053c13032b
Subject: Re: [PHP-DEV] Modern practices ...
From: arvids.godjuks@gmail.com (Arvids Godjuks)

--001a11442bb4aec45b053c13032b
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

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
other projects.
Not to mention that I do really juggle between 5.5, 5.6 and 7.0 versions
right now (and moving things to 7.0 as I'm able to).
Even for Laravel I do a per project install of homestead. And I also work
under Windows, many of my colleagues do Linux or Mac OS. Having a fully
self-contained projects helps to avoid issues between our systems.

I also do cleanup wm's that I do not need for some time, that clears out
the space on the disks, especially when databases are several GB big.

On Fri, 9 Sep 2016, 15:33 Ferenc Kovacs, <tyra3l@gmail.com> wrote:

> On Fri, Sep 9, 2016 at 1:45 PM, Lester Caine <lester@lsces.co.uk> 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 development -
> > command line - tools that PEAR currently manages happily. I AM trying t=
o
> > learn composer, and I can see now how it can be used, but simply passin=
g
> > the buck to getcomposer is not the way to use it for a default PHP
> > installation.
>
>
> composer is proven to be capable managing those use-cases but it isn't ou=
r
> duty to write out the detailed migration guides for every usecase between
> PEAR and composer.
> our duty as the php-src group is that we provide a way which allows the
> management of the pecl extensions (pickle install and maybe providing an
> alternative for pecl package) and tell people how can they install PEAR i=
f
> they still need it (https://pear.php.net/manual/en/installation.php)
> for the record most distributors already decouple PEAR from the base php
> install (php-pear is a separate optional package on debian/ubuntu, the
> windows binaries doesn't have PEAR at all, you have to manually install i=
t
> there, etc.) and from the php-src point of view we only use it to provide=
 a
> way of installing pecl extensions, which will be solved with pickle so
> while educating people to migrate their workflows from PEAR to composer i=
s
> a noble goal, but it isn't our responsibilities and we don't have to solv=
e
> that to be able to replace our php c extension management tool shipped wi=
th
> the core.
>
> --
> Ferenc Kov=C3=A1cs
> @Tyr43l - http://tyrael.hu
>

--001a11442bb4aec45b053c13032b--