Newsgroups: php.internals,php.internals.win
Path: news.php.net
Xref: news.php.net php.internals:125476 php.internals.win:1296
Precedence: bulk
MIME-Version: 1.0
References: <cca18b22-9bf4-41dd-9673-e654a5d76794@gmx.de>
In-Reply-To: <cca18b22-9bf4-41dd-9673-e654a5d76794@gmx.de>
Date: Sun, 8 Sep 2024 16:50:41 +0700
Message-ID: <CAEZPtU62qZmg67q1JumbWbTgrKX2-eUbZAp8+t=QzOAbvnk01w@mail.gmail.com>
Subject: [PHP-DEV] Re: [INTERNALS-WIN] Maintain Windows PHP dependency builds in a GH repo
To: "Christoph M. Becker" <cmbecker69@gmx.de>
Cc: PHP internals list <internals@lists.php.net>, internals-win <internals-win@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
From: pierre.php@gmail.com (Pierre Joye)

Hi Christoph,

On Sun, Sep 8, 2024 at 4:32=E2=80=AFPM Christoph M. Becker <cmbecker69@gmx.=
de> wrote:

> * the process is prone to error

Originally, it was thought to do first this (painful) manual process
to validate the flow. Then the plan was to use the releases in each
dep's repository. Having one repository to define which version-build
is needed per php version (incl patch version, f.e. security update).
That has never been done.

It was also a step required for out of php-src extension builds
(pickle partially has it, no idea where the new tool stands about
this). But that's a bit off topic here :)

> What do you think?

100% for it.

> Would this require the RFC process?

A documentation for sure, especially for external developers
(nativephp, roadrunner, etc) so they can use it for their own flows.

Best,
--=20
Pierre

@pierrejoye | http://www.libgd.org