Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:95893
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.214 cause and error)
To: internals@lists.php.net
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>
 <52ae5494-f466-ac4d-c166-d47752b13344@lsces.co.uk>
Message-ID: <32c3a330-cdfa-f310-85d7-d01eacbf3b86@lsces.co.uk>
Date: Sat, 10 Sep 2016 09:32:11 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.2
MIME-Version: 1.0
In-Reply-To: <52ae5494-f466-ac4d-c166-d47752b13344@lsces.co.uk>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Modern practices ...
From: lester@lsces.co.uk (Lester Caine)

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 been rather rare, and I
> was using a stacked version when I did ... which is another alternative
> to distributions on windows.

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 source ... it was a thread on this list
in 2011.

The problem that we were discussing at the time was availability not
only of PHP on windows but also Apache, and the fact that neither
project provides official builds on windows. While there were 'free'
paths to do your own builds on windows and I had documented my own
process at that time. These were NOT acceptable by government agencies
to provide audited installations. Windows applications come pre-compiled
and while I think that the more modern build paths can be download for
free they are not free for commercial use? An 'official' compiled build
is a requirement for windows. Although that does not necessarily need to
be provided by PHP. Apachelounge is an approved source amongst my customers.

I think I am right in saying Pierre originally needed pickle so that
PEAR could be dropped in the windows? So the only element left is
bundling PEAR with the source distribution. I've not had to worry about
PHP7 on windows as yet as the few sites were are allowed to use it are
linux servers, but it will come a point when we need to audit a PHP7
windows installation, along with a web server. And it looks as if while
5 years ago nginx was ahead of apache, the commercialization of the
former is taking it off the play list :( Just when I've got it working
nicely as a background to testing multiple copies of PHP on the same
code. This is about making PHP easily available across the board and
while windows may now be confined to the desktop machine, it is still
more popular than linux on commercial and government systems?

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk