Hi PHP Internals,
Right now, the libsodium PECL package is in the beta channel. Would it be
possible to include libsodium as a core extension in PHP 7? If so, what
hurdles would need to be cleared before that happens?
http://doc.libsodium.org/
http://pecl.php.net/package/libsodium
https://github.com/jedisct1/libsodium-php
Thanks,
Scott
P.S. I'm cc'ing Frank Denis on this initial email.
Evening Scott,
We should only consider moving an extension from PECL to core if that
extension is in wide use.
In addition to having a properly established user base, it's a good
idea to have a stable API since the development workflow (or pace) for core
extensions is restricted by the release cycle of PHP.
Even when an extension has a good userbase and a stable API, it doesn't
always make sense to bundle as a core extension, if you look at the top of
the list at the extensions with millions of downloads; there's nothing to
actually gain from bundling these extensions in the core distribution. So I
would say that there needs to be some benefit in terms of integration,
maintainability, or something of that sort.
libsodium is too young to seriously consider bundling right now I think.
Cheers
Joe
On Fri, Jan 2, 2015 at 5:05 PM, Scott Arciszewski kobrasrealm@gmail.com
wrote:
Hi PHP Internals,
Right now, the libsodium PECL package is in the beta channel. Would it be
possible to include libsodium as a core extension in PHP 7? If so, what
hurdles would need to be cleared before that happens?http://doc.libsodium.org/
http://pecl.php.net/package/libsodium
https://github.com/jedisct1/libsodium-phpThanks,
ScottP.S. I'm cc'ing Frank Denis on this initial email.
So, PHP 8 then?
Evening Scott,
We should only consider moving an extension from PECL to core if that
extension is in wide use.
In addition to having a properly established user base, it's a good
idea to have a stable API since the development workflow (or pace) for core
extensions is restricted by the release cycle of PHP.Even when an extension has a good userbase and a stable API, it
doesn't always make sense to bundle as a core extension, if you look at the
top of the list at the extensions with millions of downloads; there's
nothing to actually gain from bundling these extensions in the core
distribution. So I would say that there needs to be some benefit in terms
of integration, maintainability, or something of that sort.libsodium is too young to seriously consider bundling right now I
think.
Cheers
JoeOn Fri, Jan 2, 2015 at 5:05 PM, Scott Arciszewski kobrasrealm@gmail.com
wrote:Hi PHP Internals,
Right now, the libsodium PECL package is in the beta channel. Would it be
possible to include libsodium as a core extension in PHP 7? If so, what
hurdles would need to be cleared before that happens?http://doc.libsodium.org/
http://pecl.php.net/package/libsodium
https://github.com/jedisct1/libsodium-phpThanks,
ScottP.S. I'm cc'ing Frank Denis on this initial email.
hi,
Hi PHP Internals,
Right now, the libsodium PECL package is in the beta channel. Would it be
possible to include libsodium as a core extension in PHP 7? If so, what
hurdles would need to be cleared before that happens?http://doc.libsodium.org/
http://pecl.php.net/package/libsodium
https://github.com/jedisct1/libsodium-php
It is possible, however I am not a big fan of its APIs. Mapping one to
one the library APIs may sound nice but it is actually not a good
thing in this case in my humble opinion. Many functions do not make
sense to expose directly or not using the same methods.
That being said, I like libsodium, used it in a couple of projects
(not php related) :)
Cheers,
Pierre
@pierrejoye | http://www.libgd.org
Right now, the libsodium PECL package is in the beta channel. Would it be
possible to include libsodium as a core extension in PHP 7? If so, what
hurdles would need to be cleared before that happens?
This should be an FAQ, maybe somebody can put it on the wiki or
somewhere:
For most users it doesn't matter if an extension is bundled or
distributed via PECL. Once Linux/Unix distributors get a hand on it they
package it as an independent package, independently from being in core
or not and the user has to install the "phpX-foo" package. For Windows
this is similar - most extensions are provided as dll which has to be
activated. The only once for whom this is a notable difference are the
ones who build PHP themselves, but for them it shouldn't be a big
hurdle.
Having it in PECL means that it simplifies PHP release process (one less
moving piece) and the maintainers are more flexible in regards to
evolving the extension API by not being bound to PHP's stricter BC
rules.
By being bundled (in theory) it gets more eyes looking at it (while we
have enough bundled extensions which receive barely attention as a
counter-prove)
It has to be bundled if we want to force it on all users (we hardly do
that) or some other core components depend on it.
In my personal opinion we should continue moving stuff out instead of
in.
johannes
You're right, a cursory Google search reveals that someone is maintaining a
php5-nacl package that uses libsodium. This simplifies instructions
greatly! :D
Right now, the libsodium PECL package is in the beta channel. Would it be
possible to include libsodium as a core extension in PHP 7? If so, what
hurdles would need to be cleared before that happens?This should be an FAQ, maybe somebody can put it on the wiki or
somewhere:For most users it doesn't matter if an extension is bundled or
distributed via PECL. Once Linux/Unix distributors get a hand on it they
package it as an independent package, independently from being in core
or not and the user has to install the "phpX-foo" package. For Windows
this is similar - most extensions are provided as dll which has to be
activated. The only once for whom this is a notable difference are the
ones who build PHP themselves, but for them it shouldn't be a big
hurdle.Having it in PECL means that it simplifies PHP release process (one less
moving piece) and the maintainers are more flexible in regards to
evolving the extension API by not being bound to PHP's stricter BC
rules.By being bundled (in theory) it gets more eyes looking at it (while we
have enough bundled extensions which receive barely attention as a
counter-prove)It has to be bundled if we want to force it on all users (we hardly do
that) or some other core components depend on it.In my personal opinion we should continue moving stuff out instead of
in.johannes