Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107321
To: Levi Morrison <levim@php.net>, internals <internals@lists.php.net>
References: <CAFMT4Nrmu4Gdaj6Gqr=dHJU9wgHT4XVvtLGEObwcXVSq1N_yWw@mail.gmail.com>
Message-ID: <092d26f1-39b9-d621-1955-4585b4ed1633@beccati.com>
Date: Thu, 26 Sep 2019 07:39:55 +0200
MIME-Version: 1.0
In-Reply-To: <CAFMT4Nrmu4Gdaj6Gqr=dHJU9wgHT4XVvtLGEObwcXVSq1N_yWw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Default include_path
From: php@beccati.com (Matteo Beccati)

Hi Levi,

On 23/09/2019 00:21, Levi Morrison wrote:
> Hello Internals,
> 
> I think we should keep this include directory, separate it from pear, and
> always create it. It is sometimes useful today, and I think in the future
> it might be helpful to have it if we ever create "extensions" in PHP.
> 
> Any objections?

Yup. Realistically, very few will require such directory without PEAR.
Managing common PEAR dependencies has always been a hell of a problem
and I certainly wouldn't miss it.

If someone needs such library code sharing, they are surely more than
capable to configure the server as they please, without having to put
their code into a system directory.


Cheers
-- 
Matteo Beccati

Development & Consulting - http://www.beccati.com/