Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121843
MIME-Version: 1.0
References: <c14d3aed-bc05-47df-843a-54805afb5c9c@php.net> <62C2C517-B14F-445E-AD3B-7915544B17B2@php.net>
 <CAJp_myXanVM7Lj2DLWQ48kC440kU_XkQxzZg5fVdg42YLZr-OQ@mail.gmail.com>
In-Reply-To: <CAJp_myXanVM7Lj2DLWQ48kC440kU_XkQxzZg5fVdg42YLZr-OQ@mail.gmail.com>
Date: Wed, 29 Nov 2023 01:54:22 +0100
Message-ID: <CADyq6sJA5_SKn1N09xVAb8p3OPkG9pTYK4mF0VMudR0TrMhG+g@mail.gmail.com>
To: "Matthew Weier O'Phinney" <mweierophinney@gmail.com>
Cc: Derick Rethans <derick@php.net>, PHP Developers Mailing List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000090bf6a060b3ffafd"
Subject: Re: [PHP-DEV] Reproducible Builds
From: ocramius@gmail.com (Marco Pivetta)

--00000000000090bf6a060b3ffafd
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, 29 Nov 2023 at 01:48, Matthew Weier O'Phinney <
mweierophinney@gmail.com> wrote:

> On Tue, Nov 28, 2023, 5:28=E2=80=AFPM Derick Rethans <derick@php.net> wro=
te:
>
> > 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
> date
> > 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
> the
> > output of phpinfo(), "php -i", etc.?
> >
> > It is really useful for the development versions of PHP. Knowing whethe=
r
> > 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.
>

Also, refs have a timestamp :-)

Marco Pivetta

https://mastodon.social/@ocramius

https://ocramius.github.io/

--00000000000090bf6a060b3ffafd--