From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] default php-ext status
Date: Mon, 22 Apr 2024 12:49:25 -0400 [thread overview]
Message-ID: <4f932586b3fb34a202d53ede4b0da30976074ddd.camel@gentoo.org> (raw)
In-Reply-To: <e1b14f22-27c4-411f-b657-1d5f4fefae7b@uls.co.za>
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
> certainly is not a desirable option, so perhaps INSTALL_MASK
> (per-package env) is the best solution ... ?
You can replace the symlinks with empty files. The package manager
should then refuse to overwrite them. It _looks_ wrong (why are these
non-active extensions in ext-active?), but it's the easiest solution.
I think the default should be for the extensions to be per-SAPI
disabled and for users to enable them by creating the symlinks. (The
"ext" and "ext-active" design screams this.) That would be an easy
change to php-ext-source-r3.eclass but risks breaking everyone's web
servers if we do it without news items and/or ewarnings.
There's nobody in the PHP project at the moment. If you want to make an
-r4 of the eclass and handle the paperwork, by all means...
next prev parent reply other threads:[~2024-04-22 16:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 14:46 [gentoo-dev] default php-ext status Jaco Kroon
2024-04-22 16:49 ` Michael Orlitzky [this message]
2024-04-23 11:05 ` Jaco Kroon
2024-04-25 12:27 ` Michael Orlitzky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4f932586b3fb34a202d53ede4b0da30976074ddd.camel@gentoo.org \
--to=mjo@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox