Hi!
I've just learned from ext/gd/libgd/README that the bundled GD library
is actually a fork of libgd, which was quite a surprise to me as I
thought gd is handled similar to pcre and sqlite3.
Anyhow, I wonder how to deal with bug reports for PHP's gd extension, if
they point to a common bug in libgd. Shall I make PRs against php-src
and report the issue to libgd?
--
Christoph M. Becker
Hi,
Hi!
I've just learned from ext/gd/libgd/README that the bundled GD library
is actually a fork of libgd, which was quite a surprise to me as I
thought gd is handled similar to pcre and sqlite3.
It is somehow similar as it was an actual fork before we took over the
upstream version.
Due to own BC reasons we cannot be fully synced with upstream at this stage
but a large part of the library is.
Anyhow, I wonder how to deal with bug reports for PHP's gd extension, if
they point to a common bug in libgd. Shall I make PRs against php-src
and report the issue to libgd?
Either way. If you can do both it will be fantastic. But as the same
persons maintain both sides, we do our best to keep them synced :)
Cheers,
Pierre
Pierre Joye wrote:
Hi,
Hi!
I've just learned from ext/gd/libgd/README that the bundled GD library
is actually a fork of libgd, which was quite a surprise to me as I
thought gd is handled similar to pcre and sqlite3.It is somehow similar as it was an actual fork before we took over the
upstream version.Due to own BC reasons we cannot be fully synced with upstream at this stage
but a large part of the library is.
Ah, I see. Thanks for the explanation. :)
Anyhow, I wonder how to deal with bug reports for PHP's gd extension, if
they point to a common bug in libgd. Shall I make PRs against php-src
and report the issue to libgd?Either way. If you can do both it will be fantastic. But as the same
persons maintain both sides, we do our best to keep them synced :)
Okay, so I'll do both. :)
--
Christoph M. Becker