Edit report at https://bugs.php.net/bug.php?id=63520&edit=1
ID: 63520
Comment by: ond...@php.net
Reported by: kaplan at debian dot org
Summary: JSON extension includes a problematic license
statement
Status: Assigned
Type: Bug
Package: JSON related
PHP Version: Irrelevant
Assigned To: remi
Block user comment: N
Private report: N
New Comment:
Stas: Of course it's a PHP bug. PHP don't live in a vacuum, but has thriving
ecosystem of various users/packagers/distributors/distributions/etc. and they
are
all affected by the choice you (as PHP) make.
It's not healthy to dug the head into the sand and pretend that it's not a
_PHP_
bug, since it affects the users of PHP.
Previous Comments:
------------------------------------------------------------------------
[2013-08-22 22:01:39] kap...@php.net
Stas: We (PHP) provide the code, and the eco system clearly has a problem with
it. We could either keep ignoring it while they provide a replacement code, or
adopt it officially to make everyone happy.
------------------------------------------------------------------------
[2013-08-22 21:52:19] shitty at gmail dot com
Not evil???????... come on!!!!!!!
------------------------------------------------------------------------
[2013-08-21 18:47:57] s...@php.net
How this is a PHP bug?
------------------------------------------------------------------------
[2013-07-17 15:18:33] r...@php.net
@seld Mandriva/Fedora/Debian have drop json non-free extension but provides
jsonc dropin alternative (php5-json 1.3.1 for debian).
So, your comment is not PHP related. See debian packager to have this package
installed when needed (pulled by main php package for Fedora).
------------------------------------------------------------------------
[2013-07-17 14:24:32] s...@php.net
What's the status here Remi? Can we have a regular Debian release including the
JSON ext before this hits testing/stable? We had a first issue on Composer
today because someone was missing the json ext [1], using Ubuntu 13.10.
If this isn't resolved soon Ubuntu's next release won't have json enabled by
default and we'll have a support shitstorm on our hands, so please don't do
Evil because of a dubious license statement. Given the prevalence of JSON APIs
and such these days, it's not just Composer that will be affected, so removing
it before having a replacement in place was really an unhelpful decision IMO.
[1] https://github.com/composer/composer/issues/2092
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=63520
--
Edit this bug report at https://bugs.php.net/bug.php?id=63520&edit=1
