Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:81035
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.214 cause and error)
Message-ID: <54C20D0B.4060104@lsces.co.uk>
Date: Fri, 23 Jan 2015 08:57:47 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <54C1261D.7080009@php.net> <CAEZPtU6HE6cf38xPpS6M9QvP_f7jrcK5Aka=1mJKPh30eb36Lg@mail.gmail.com> <21F16F7C-CEBE-4498-A539-E2E66EE147F7@php.net>
In-Reply-To: <21F16F7C-CEBE-4498-A539-E2E66EE147F7@php.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Subject: Packaging in general - was Re: [PHP-DEV] [RFC] pecl_http
From: lester@lsces.co.uk (Lester Caine)

On 23/01/15 08:27, Michael Wallner wrote:
> Well, I’m not the one to tell you that :) If I didn’t find it useful, I wouldn’t have built it.
> Don’t hesitate, if there are questions about what they conceptually are trying to accomplish.
> 
> I think a short discussion about where to put the dependant code and noting the outcome in the RFC could be the way to go. I guess just a few people who think that pecl_http is about to be included would suffice.

I started using PHP one windows, and so have always viewed it as a
smaller core and a series of modules. SUSE continues that model and I
see no reason to change now, so in my book it is the the current
bundling and enabling by default that has always been the wrong
approach. I simply enable the elements I need and leave out all the
other stuff which I don't. So the debate should be if other 'dependant
code' exists. A large section of the ini file relates to modules which
may well not be enabled so that gets deleted and moved to the relevant
sub.ini .

You are already talking about pushing php_interbase and other extensions
into pecl, so they can be ignored but we got agreement a long time ago
that no one database would be enabled by default, so all should be
easily available. I would probably add that for a long time now I think
most distributions have bundled mysql and mysqli in the one package, so
the idea of removing mysql may not be so easy to achieve.

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk