Re: [RFC] Extension Prepend Files
| From: | Pierre Joye | Date: | Wed, 07 Jan 2015 10:21:42 +0000 |
| Subject: | Re: [RFC] Extension Prepend Files | ||
| References: | 1 2 3 4 5 6 7 8 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-80250@lists.php.net to get a copy of this message | ||
On Jan 7, 2015 5:15 PM, "Derick Rethans" <derick@php.net> wrote:
>
> On Tue, 6 Jan 2015, Stanislav Malyshev wrote:
>
> > > But, if we consider the PHP code as an integral part of the
> > > extension, this should be avoided, as C and PHP code need to be kept
> > > in sync.
> >
> > Again, there is a multitude of solutions for this, all in the realm of
> > packaging. It's not like we've just encountered the idea of software
> > package having more than one file.
>
> There is currently no way to install an extension and a PHP library
> package at the same time. "pecl" can't install PHP libraries, and
> "composer" can't install extensions. And even if it did, keeping the
> versions in sync is not easy at all. Only way to solve this properly is
> to allow PHP code embeded in the extension. Just like the couchdb ext
> does, or Benjamin wants to do with the qafooprofiler, or HHVM does it
> through HNI.
Pickle integration is almost finished, that solves your worries about
composer and pecl extensions.
And if you ready other replies carefully I have proposed cleaner solution
(than bundling scripts).
And no, bundling code is not the easy way, it is a can of worms, to
implement, maintain and even worst, for distros.