Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121842
MIME-Version: 1.0
References: <c14d3aed-bc05-47df-843a-54805afb5c9c@php.net> <62C2C517-B14F-445E-AD3B-7915544B17B2@php.net>
In-Reply-To: <62C2C517-B14F-445E-AD3B-7915544B17B2@php.net>
Date: Tue, 28 Nov 2023 18:48:28 -0600
Message-ID: <CAJp_myXanVM7Lj2DLWQ48kC440kU_XkQxzZg5fVdg42YLZr-OQ@mail.gmail.com>
To: Derick Rethans <derick@php.net>
Cc: PHP Developers Mailing List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000005392e4060b3fe581"
Subject: Re: [PHP-DEV] Reproducible Builds
From: mweierophinney@gmail.com ("Matthew Weier O'Phinney")

--0000000000005392e4060b3fe581
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, Nov 28, 2023, 5:28=E2=80=AFPM Derick Rethans <derick@php.net> wrote=
:

> On 28 November 2023 17:28:18 GMT, Sebastian Bergmann <sebastian@php.net>
> wrote:
>
> >While we could probably replace __DATE__ and __TIME__ with
> SOURCE_DATE_EPOCH [3] [4], I cannot help but wonder whether having the da=
te
> and time when the executable was built in the executable is actually
> useful. How attached are we to having the date and time of the build in t=
he
> output of phpinfo(), "php -i", etc.?
>
> It is really useful for the development versions of PHP. Knowing whether
> your are running a PHP-dev from last week or last month is important.


Would Marco's suggestion of using a git hash solve that? You'd then get
both a reproducible build AND know when/what it was generated from.

>
>
>
>

--0000000000005392e4060b3fe581--