Create php extension ini files with .sample extension
to prevent subsequent upgrades from clobbering the, possibly,
user-modified .ini files.
Details
Details
- Reviewers
ale bofh - Group Reviewers
portmgr - Commits
- R11:34212762f08d: php.mk: Create php extension ini files as sample
Diff Detail
Diff Detail
- Repository
- R11 FreeBSD ports repository
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
Comment Actions
In theory those files were not designed to be modified by the user. What's the use case that requires it and that cannot be done via another php configuration file?
Comment Actions
The actual use case, for me, is that I have an unified set of extensions of which one (opcache) is causing problems in one particular installation. That's why I want to be able to comment it out without subsequent update to activate it again.
Moreover, it's a handy place to put extension's configuration into.
Comment Actions
As you approve it I will run a smaller exp-run on this and revert back after I finish my exp-run on newer version of php81 and php82. :)
Comment Actions
I can't see any potential drawback in this change, so if it works as expected I approve it. Waiting for your exp-run feeback.