From: Jaco Kroon <jaco@uls.co.za>
To: gentoo development <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] default php-ext status
Date: Mon, 22 Apr 2024 16:46:43 +0200 [thread overview]
Message-ID: <e1b14f22-27c4-411f-b657-1d5f4fefae7b@uls.co.za> (raw)
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 themselves:
plastiekpoot [16:43:09] /etc/php (master) # ls -lah */ext-active/xdebug.ini
lrwxrwxrwx 1 root root 17 Apr 22 15:36
apache2-php8.1/ext-active/xdebug.ini -> ../ext/xdebug.ini
lrwxrwxrwx 1 root root 17 Apr 22 15:36 cli-php8.1/ext-active/xdebug.ini
-> ../ext/xdebug.ini
lrwxrwxrwx 1 root root 17 Apr 22 15:36 fpm-php8.1/ext-active/xdebug.ini
-> ../ext/xdebug.ini
plastiekpoot [16:43:15] /etc/php (master) # rm
apache2-php8.1/ext-active/xdebug.ini
plastiekpoot [16:43:21] /etc/php (master) # emerge -av xdebug
...
plastiekpoot [16:43:52] /etc/php (master) # ls -lah */ext-active/xdebug.ini
lrwxrwxrwx 1 root root 17 Apr 22 16:43
apache2-php8.1/ext-active/xdebug.ini -> ../ext/xdebug.ini
lrwxrwxrwx 1 root root 17 Apr 22 16:43 cli-php8.1/ext-active/xdebug.ini
-> ../ext/xdebug.ini
lrwxrwxrwx 1 root root 17 Apr 22 16:43 fpm-php8.1/ext-active/xdebug.ini
-> ../ext/xdebug.ini
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 ... ?
Kind regards,
Jaco
next reply other threads:[~2024-04-22 14:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 14:46 Jaco Kroon [this message]
2024-04-22 16:49 ` [gentoo-dev] default php-ext status Michael Orlitzky
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=e1b14f22-27c4-411f-b657-1d5f4fefae7b@uls.co.za \
--to=jaco@uls.co.za \
--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