Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:114761
MIME-Version: 1.0
References: <CAA6+j4twA=gLkm3BQ6Hfv10e7sK7ci7jgxbZd0u=wvqJLM9hug@mail.gmail.com>
 <03294c9d-6cb3-35ec-913e-6adf8ac0b164@php.net>
In-Reply-To: <03294c9d-6cb3-35ec-913e-6adf8ac0b164@php.net>
Date: Mon, 7 Jun 2021 16:10:21 +0700
Message-ID: <CAEZPtU7WjWDTr4nVo+YgaHKsMwQk49MmdbQm8OKumaTKshfj4A@mail.gmail.com>
To: Remi Collet <remi@php.net>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000018b72505c4296a5a"
Subject: Re: [PHP-DEV] Propagating AVIF support from libgd into PHP's bundled gd
From: pierre.php@gmail.com (Pierre Joye)

--00000000000018b72505c4296a5a
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hj Remi! :)

On Mon, Jun 7, 2021, 3:01 PM Remi Collet <remi@php.net> wrote:

> Le 04/06/2021 =C3=A0 16:36, Ben Morss via internals a =C3=A9crit :
>
> > ... I created a PR to propagate libgd's AVIF
> > support into PHP's bundled gd fork...
>
> Does it really make sense to keep maintaining this fork ?
>
> Having to maintain 2 (quite) different code and picking
> piece from one to other seems a waste of energy.
>
> I really think that we'll need to re-sync bundled gd
> with upstream and only keep it as an alternative for
> people without system gd (and perhaps even drop it later)
>


it is more or less the same.

If we want to drop the use of php malloc, could be easy then.

but this is not the topic of this discussion though  ")


>
> My 0.02cts
>
> Remi
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: https://www.php.net/unsub.php
>
>

--00000000000018b72505c4296a5a--