September 22, 2019 22:email@example.com (Levi Morrison)
I've recently discovered that the default include_path is dependent on
whether pear is enabled. I don't remember the discussion but we have
decided to deprecate pear. This has the implication that going forward
there won't be a standard place for PHP code in the installation prefix.
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.
September 26, 2019 05:firstname.lastname@example.org (Matteo Beccati)
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.
Development & Consulting - http://www.beccati.com/