On Mon, Feb 22, 2016, at 07:46, Vincas Dargis wrote: > On Tue, 19 May 2015 16:02:48 +0200 Florian Baumann <f...@noqqe.de> wrote: > > Where is the advantage of the old flag? > > If it is done like tutorials suggests, then there will be two libgd > libraries in Debian: one in upstream libgd2 package, AND another > statically linked inside PHP itself. In this way, handling bugs and > security issues would be harder, so Debian policy does not allow that, > IF I understand it correctly.
You understand it precisely. > So either upstream libgd developers should go in sync with PHP fork... > or Debian should use PHP libgd instead of upstream package... or.. I > dunno... I helped making libgd 2.0.x releases to happen, that brought the library almost in sync with PHP libgd2 fork. The libgd has recently got some traction and got moved to github: https://github.com/libgd, but still more developers contributing code would be beneficial to the project. I would suggest a third option: everybody who can code and care about getting imageantialias to Debian PHP to go to libgd project and contribute a working code that would get a required library support in the standalone libgd2 (while not breaking existing ABI/API). Cheers, -- Ondřej Surý <ond...@sury.org> Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
