Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:101744
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmx.de designates 212.227.17.21 as permitted sender)
To: PHP internals <internals@lists.php.net>
Message-ID: <dc356798-43b3-c107-9de0-2df2caeca65b@gmx.de>
Date: Fri, 2 Feb 2018 23:45:58 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
 Thunderbird/52.6.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Language: de-DE
Content-Transfer-Encoding: 7bit
Subject: What to do with bundled GD's version info?
From: cmbecker69@gmx.de ("Christoph M. Becker")

Hi everybody!

Please consider the following script:

  <?php
  echo gd_info()['GD Version'], PHP_EOL,
      GD_MAJOR_VERSION, '.', GD_MINOR_VERSION, '.',
      GD_RELEASE_VERSION, PHP_EOL;

If PHP is compiled with the *bundled* libgd, it outputs since at least
PHP 5.3.25/5.4.1:

  bundled (2.1.0 compatible)
  2.0.35

Obviously, that would mean there have been no relevant changes to the
bundled libgd for years, which is not true.  Even worse, there has never
been a bundled libgd version which was fully compatible to system libgd
2.1.0, ever.  Presently, we're somewhat close to libgd 2.2.5, but still
we couldn't claim full compatibility.  Of course, in the long run the
goal is to finally bundle an unmodified copy of the upstream library,
but for now that appears out of reach.

So the question is how to handle the version information of the bundled
libgd for the time being.   With regard to gd_info()['GD Version'] just
saying "bundled" (without any compatibility statement) might be a good
solution.  However, I'm at a loss how to handle GD_*_VERSION.  Any ideas?

-- 
Christoph M. Becker