Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:99141
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain canonical.com from 209.85.161.171 cause and error)
MIME-Version: 1.0
In-Reply-To: <CACXBjuiAkBUX3yyyCWF3gJxf6qv0Q2Pc-M=51wv05cFoMe4Msg@mail.gmail.com>
References: <CAMxnTAN+-hJLWebMFDHu6zVafhC4OYsADygaQ+Jd+bp4SrL23A@mail.gmail.com>
 <44F2A014-7DA2-49EF-A706-342C5657B615@gmail.com> <CAMxnTAOeGy+kkDgu3UUQ_sRHE_bmfcuUuNzQeydDFpBpJAjgTA@mail.gmail.com>
 <1494430967.4177.11.camel@schlueters.de> <CACXBjuiAkBUX3yyyCWF3gJxf6qv0Q2Pc-M=51wv05cFoMe4Msg@mail.gmail.com>
Date: Wed, 24 May 2017 12:36:04 +0100
Message-ID: <CAMxnTANaGyBbbKrSTrVp1CFnFBUQDxKMZhCH+TtTt==6jO8DHA@mail.gmail.com>
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Cc: =?UTF-8?Q?Johannes_Schl=C3=BCter?= <johannes@schlueters.de>, 
	Rowan Collins <rowan.collins@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Snapping php
From: alan.pope@canonical.com (Alan Pope)

Hi again,

I appreciate the comments from everyone on the subject of snapping
php. I'm keen to pass your honest feedback to our team, so we can
understand why some software developers aren't keen on investing time
to make a snap.

What's the rationale behind not doing binary releases beyond Windows?
Is that a historical legacy because distro people did that for you, so
why bother, or some other reason? Also, I'm interested to know why
it's not seen as useful to have an automated build on each commit, and
an easy single-command way to get stable builds to stable channels?

All the best,
Al

On 10 May 2017 at 18:25, Rasmus Lerdorf <rasmus@lerdorf.com> wrote:
> Also note that we don't do binary release outside of Windows. We leave it=
 up
> to the various distributions. If this Snap thing, which I have also never
> heard of, has the equivalent of an rpm .spec file that you wish to
> contribute and keep up to date we can add that, but anything beyond that =
is
> out of scope for us (including helping you get the word out about Snap). =
You
> are welcome to pull the latest branches and automatically build snaps of
> whatever versions of PHP you like, of course. It doesn't sound like you n=
eed
> our help for that.
>
> -Rasmus
>
> On Wed, May 10, 2017 at 8:42 AM, Johannes Schl=C3=BCter <johannes@schluet=
ers.de>
> wrote:
>>
>> Hey,
>>
>> On Mi, 2017-05-10 at 15:05 +0100, Alan Pope wrote:
>> > A notable example would be NextCloud, in which the snap
>> > contains Apache, MySql, PHP and NextCloud itself.
>>
>> To my understanding this is the right place for this - snap is for an
>> "application" but aside from some developers PHP isn't the application
>> people are looking for. They are maybe looking for "a webserver with
>> PHP enabled" or NextCloud/Wordpress/moodle/whatever. It's a bit like
>> snapping up stdlibc ;-)
>>
>>
>> If somebody wants to add a snapfile or whatever might be needed we
>> could certainly add it  Maybe it would see more maintenance than our
>> rpm spec file, which apparently hasn't seen a real change since 1999 :-
>> )
>>
>>
>>
>> johhannes
>>
>> --
>> PHP Internals - PHP Runtime Development Mailing List
>> To unsubscribe, visit: http://www.php.net/unsub.php
>>
>



--=20
Alan Pope
Snap Advocate

Canonical - Ubuntu Engineering and Services
+44 (0) 7973 620 164
alan.pope@canonical.com
http://ubuntu.com/