@Skoop I guess there is none, as rector package is delivered as a shim only requiring a specific phpstan version: packagist.org/packages/rector/… So it already is like a phar shipped as composer package in some way.
@danielsiepmann but that's the thing: we're doing a lot of upgrades right now, and dependency-issues are the biggest problem we run into. mostly issues with dependencies of dev-tools. so I was hoping to put all QA/analysis tools as PHARs to minimize those issues. Everything is a PHAR, but not rector. and that requires PHPStan again. Opening up the issues again.
@Skoop I feel you. There's always one piece of the puzzle that does not work the I want things to work which then makes my whole idea pointless /cc @heiglandreas
@Skoop That is the "problem" with PHARs. They are great for standalone tools. But as soon as you need plugins, dependencies or whatever, you get either into a lot of trouble or .. let's not discuss the OR...
@heiglandreas@sven Right now, I'm leaning towards using Phive to install PHPUnit, PHP CS Fixer, PHPStan. And using a separate composer.json for Rector, which may install PHPStan, but that will only be for Rector, I'd use the PHAR for actually running PHPStan.
@Skoop@sven Depending on how Rector calls PHPStan you can even use the replace config inside the composer.json to make it not install PHPStan and then use PHPStan from the tools-directory...
Add comment