Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:72426
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.49 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
In-Reply-To: <52F0C86A.9010805@lsces.co.uk>
References: <52F0C86A.9010805@lsces.co.uk>
Date: Mon, 10 Feb 2014 11:25:54 +0900
Message-ID: <CAGa2bXZJQB2Rqq+0nh+fD4NZ_bgPVH8mVe8hL2Qr8vEXF2FABw@mail.gmail.com>
To: Lester Caine <lester@lsces.co.uk>
Cc: PHP Developers Mailing List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e0160b61881e54004f204118a
Subject: Re: [PHP-DEV] Modular distributions
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--089e0160b61881e54004f204118a
Content-Type: text/plain; charset=UTF-8

Hi Lester,

On Tue, Feb 4, 2014 at 8:00 PM, Lester Caine <lester@lsces.co.uk> wrote:

> The main focus here though is to more easily allow 'development' versions
> of extension improvements to be used in the field, rather than having a
> fully bundled update? In the past maintaining the windows installations has
> been by just updating a single extension, and formalising that still makes
> sense to me although I know that many of you prefer the 'core bundle' model
> which includes many packages that never actually get used by some of us. A
> modular model is used by the Linux distributions and seems to be preferred
> anyway?


I like the idea overall.
We may have php-src/ext/ as standard module that distributors must
compile statically (or should be loaded by default) and
php-src/bundled-ext/
as optional modules that may be loaded optionally.

We may include well maintained/mature PECL modules php-src/bundled-ext/
and bundled/ext may have it's own web pages for newer releases.

However, I also like the current way of distributing module as PHP package,
since I can assume capability of modules by PHP version and all I have to do
is PHP version check rather than each modules version check. It may be time
to forget about this, though.

Current way is reasonable to avoid dependency hell that other languages
have.
Convenience depends on users' usage. IMO.

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--089e0160b61881e54004f204118a--