On Tue, 2024-04-23 at 13:05 +0200, Jaco Kroon wrote:
> but how do we handle
> users making manual additions/modifications to /etc/php/ or have some
> form of "fsck" for that?)
We'd have to use a new location that doesn't collide with anything that
the user might edit, like /etc/php/*/ext-eselect
Hi,
On 2024/04/22 18:49, Michael Orlitzky wrote:
On Mon, 2024-04-22 at 16:46 +0200, Jaco Kroon wrote:
Which in my *opinion* is not desirable behaviour, but I'm open for
discussion.
xdebug.mode = off by default, but the extension still gets loaded.
Not sure if there is a sensible "solution", f
On Mon, 2024-04-22 at 16:46 +0200, Jaco Kroon wrote:
>
> Which in my *opinion* is not desirable behaviour, but I'm open for
> discussion.
>
> xdebug.mode = off by default, but the extension still gets loaded.
>
> Not sure if there is a sensible "solution", further expanding USE flags
> certain
Hi All,
For PHP modules that's getting installed, by default they all link
ext/${modulename}.ini into ext-active/ such that all modules by default
is active for all SAPIs.
Short of INSTALL_MASK, is there way to better control for sysadmins?
If I rm the symlinks, on next remerge they restore
