Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80304
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.215.10 cause and error)
Message-ID: <1420801864.19448.7.camel@kuechenschabe>
To: Scott Arciszewski <kobrasrealm@gmail.com>
Cc: PHP internals <internals@lists.php.net>, pureftpd@pureftpd.org
Date: Fri, 09 Jan 2015 12:11:04 +0100
In-Reply-To: <CAPKwhwvdVu00wp_h-NngLnVvCXRWdkUKP=RRCZWHarYzhGh+OQ@mail.gmail.com>
References: 
	<CAPKwhwvdVu00wp_h-NngLnVvCXRWdkUKP=RRCZWHarYzhGh+OQ@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] libsodium for PHP 7?
From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

On Fri, 2015-01-02 at 12:05 -0500, Scott Arciszewski wrote:
> 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