-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PSR conflict with Symfony #40
Comments
It sounds not bad. I'm thinking of something like an ENV to pass a list of extensions (not just PSR) to disable at start-up (remove them eventually). |
On the other hand, being able to turn off extensions at build time should be also a nice feature since not all users want the same amount of extensions to use. |
Feel free to propose something in either case. |
I think an ENV would do just fine. At this point I would go for a blacklist to disable certain extensions. So in my case I would pass on an ENV "EXTENSION_BLACKLIST" with value "psr" or something like that. |
Any progress on this? ;) |
Unfortunately, I couldn't find the time, but if you want to help, just let me know. |
Hi, I ran into an issue today that the PSR extension conflicts with the Symfony cache component. I therefore had to remove PSR, but as there is no "docker-php-ext-disable" (and it will not be there, see docker-library/php#220 (comment)) I tried "pecl uninstall psr". Unfortunately that created another issue:
I could of course create a PR for the removal of PSR, but it might be more interesting to have a ENV variable control the installation of PSR (and maybe other extensions).
How do you feel about this?
The text was updated successfully, but these errors were encountered: