Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107121
MIME-Version: 1.0
References: <CAF+90c8kXU9jPN4gDku_+HDqjZNbdc-aEeAP0xVjqP99MYCimQ@mail.gmail.com>
 <a3d36c20-04eb-65b0-6f65-a5f7b77d4a44@xs4all.nl>
In-Reply-To: <a3d36c20-04eb-65b0-6f65-a5f7b77d4a44@xs4all.nl>
Date: Sun, 15 Sep 2019 22:53:09 +0200
Message-ID: <CAP=4hCJipeWqWzwm5Q3p9u6ZPJE59er0hdkUMORLZch0mxdzFQ@mail.gmail.com>
To: Dik Takken <d.takken@xs4all.nl>
Cc: Nikita Popov <nikita.ppv@gmail.com>, PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000007e3d5c05929dad95"
Subject: Re: [PHP-DEV] Build instructions for Ubuntu 18.04 (and other systems)
From: carusogabriel34@gmail.com (Gabriel Caruso)

--0000000000007e3d5c05929dad95
Content-Type: text/plain; charset="UTF-8"

Hello Dik

On Sun, Sep 15, 2019, 22:42 Dik Takken <d.takken@xs4all.nl> wrote:

> On 15-09-19 20:49, Nikita Popov wrote:
> >
> > Anyone interested in doing this?
> >
>
> Hi Nikita,
>
> May I suggest to provide instructions to build using Docker? This has a
> number of advantages:
>
> * Same instructions will work on Linux, MacOS and Windows
> * No need to install build dependencies on your host
> * Spin up a MySQL container by running 'docker run mysql:version'
>
> I took this route a while ago when I needed to setup a dev environment
> and it works nicely. I could do a write-up of this route if desired.
>
> Part of the instructions could be cast into a Docker image that can be
> published on Github and Docker Hub. This image could even have the
> command to run the tests baked into the image itself. Then, anyone can
> just run
>
>     docker run php-tests:7.4
>
> to build the sources and run the tests. For development you can mount
> your local git clone in the container.
>
> Regards,
> Dik Takken
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php


The main problem with Docker and php-src is that we need to touch the OS in
order to make sure the new features and bugfixes will be compatible.

Docker create a layer on top of that, right?

Best regards,

>
>

--0000000000007e3d5c05929dad95--