Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123317
Date: Tue, 14 May 2024 10:36:06 +0100 (BST)
To: Niels Dossche <dossche.niels@gmail.com>
cc: PHP internals <internals@lists.php.net>
Subject: Re: [PHP-DEV] Stricter requirements for libxml
In-Reply-To: <42857f2f-fef7-447f-b7a8-ef92180e4768@gmail.com>
Message-ID: <56c7973d-be03-3945-8326-ff55fcda0216@php.net>
References: <42857f2f-fef7-447f-b7a8-ef92180e4768@gmail.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
From: derick@php.net (Derick Rethans)

On Fri, 10 May 2024, Niels Dossche wrote:

> Hi internals
> 
> Libxml is used as the underlying library for many PHP extensions.
> Interestingly, libxml can be built with supports for various features disabled.
> E.g. you can build libxml without XPath, Schemas, HTML, ... support.
> In that case, these features are unavailable in PHP. E.g. some classes may not be defined or functions may emit a warning instead of performing an action.
> 
> I'm thinking of proposing an RFC that puts stricter requirements on libxml at build time.
> That would make such features a requirement during PHP's build process.
> This will simplify maintenance and will also make sure that users can rely on these functionalities to always be available.
> 
> Please let me know what you think.

That seems sensible. Did you find any Linux distribution that actively 
disables these features, or is this a "just in case" kind of change?

cheers,
Derick