-
-
Notifications
You must be signed in to change notification settings - Fork 45
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
Allow phpstan/extension-installer #417
Comments
Similar here, for my case I've found that I still prefer to use Composer for
(And I use phive for |
Dealing with extensions isn't easy - as that opens the door to actual dependency handling. See #88 for details. PHPStan, if i recall correctly, is particularly problematic as it uses - for no apparent reason to me - PHPScoper when creating its phar archive. That makes it virtually impossible to install extensions for the phar distribution of it as the namespace of PHPStan or any child components is random. Unless the PHPStan authors drop that, there is nothing phive can do to make things work - even if we'd have a means of installing extensions. |
PHPUnit is actually one of the main reasons phive exits: As it's a tool with runtime impact when executing tests, collisions in packages are a nightmare. I fail to see how installing phpunit with composer is in any possible way better. Extensions to PHPUnit are best distributed as phar as well. |
@theseer It's because I use Additionally, the architecture of my project may not be very common. It's a very simple and efficient website, with no OOP and free from any PHP dependencies: https://github.com/Softcatala/pccd |
Is it possible to allow/support also
Refs cakephp/cakephp#17448
We currently have phpstan installed via phive, but also having those (depending directly on phpstan) available makes it a bit tricky.
It almost sounds like we would have to remove phpstan from phive installation back to normal require-dev.
Would be nice if those could somehow we supported as well.
Is this feasable?
The text was updated successfully, but these errors were encountered: