Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107123
To: Gabriel Caruso <carusogabriel34@gmail.com>
Cc: Nikita Popov <nikita.ppv@gmail.com>,
 PHP Internals <internals@lists.php.net>
References: <CAF+90c8kXU9jPN4gDku_+HDqjZNbdc-aEeAP0xVjqP99MYCimQ@mail.gmail.com>
 <a3d36c20-04eb-65b0-6f65-a5f7b77d4a44@xs4all.nl>
 <CAP=4hCJipeWqWzwm5Q3p9u6ZPJE59er0hdkUMORLZch0mxdzFQ@mail.gmail.com>
Message-ID: <7544e72f-4bce-170b-d2cc-e523de32d862@xs4all.nl>
Date: Sun, 15 Sep 2019 23:21:59 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <CAP=4hCJipeWqWzwm5Q3p9u6ZPJE59er0hdkUMORLZch0mxdzFQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Build instructions for Ubuntu 18.04 (and other systems)
From: d.takken@xs4all.nl (Dik Takken)

On 15-09-19 22:53, Gabriel Caruso wrote:
> 
> 
> 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?
> 

Correct. Honestly I was not considering the use case of testing
interactions with OS-specific features as one might do using a CI/CD
setup. Providing instructions that will work for every supported target
environment is not an easy thing to do.

I was thinking about the use case of local development where the
developer needs to build the sources on whatever OS he / she happens to
be using. Then, Docker makes much more sense as it provides a single
consistent environment that will work the same way for anyone.