Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:74520
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.176 as permitted sender)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
In-Reply-To: <1401193927.2998.50.camel@guybrush>
Date: Tue, 27 May 2014 15:29:22 +0200
Cc: Michael Wallner <mike@php.net>,
 PHP Internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <FDFBD40A-776A-473C-90FD-B75B2A462E60@gmail.com>
References: <CALJZF3gdNrEmr1tR05Gx35ewzydsAx58nbxkA4FzCUqVz1gRAw@mail.gmail.com> <1401193927.2998.50.camel@guybrush>
To: =?windows-1252?Q?Johannes_Schl=FCter?= <johannes@schlueters.de>
Subject: Re: [PHP-DEV] Linking and autoloading of dependent extensions
From: mike.php.net@gmail.com (Michael Wallner)

On 27 05 2014, at 14:32, Johannes Schl=FCter <johannes@schlueters.de> =
wrote:
> On Tue, 2014-05-27 at 14:13 +0200, Michael Wallner wrote:
>> I've prepared a tiny POC which enables linking and autoloading of
>> dependent extensions:
>> https://github.com/m6w6/php-src/compare/module_deps
>>=20
>> Anybody else other than me interested in this feature?
>=20
> This is a problem hurting me for a while and I'm happy you're looking
> into it! I'm not sure about the solution here, though. This solution
> assumes
>=20
>      * the extension is inside extension_dir and
>      * a specific naming scheme on the extension's shared library =
file.
>=20
> Both assumptions might be wrong and might lead to loading the wrong =
file
> when different ones are around. This will also lead to a misleading
> error message ("PHP Warning:  Module 'foo' already loaded in Unknown =
on
> line 0") where the users just tries to load it once in wrong order.

Thanks Johannes, as always you=92ve got a bigger picture than I have!
The warning should be easy to mitigate except for multiple extension INI =
entries; not sure if this is that important, though.

The second problem is a bit harder, except for source distribution =
installations where EXTENSION_DIR should be fine and PECL installs where =
I could use INI=92s extension_dir.
For relocated extension_dirs like Linux dist packages, this might indeed =
be a problem.

Thank you,
Mike