in parallel (npm) 2 „boxes“: install the tools globally: composer global require … solves conflicts between code libraries and tools does not solve conflicts between tools 2 „boxes“: separate directory for tools solves conflicts between code libraries and tools does not solve conflicts between tools
separate directory and one composer.json for each tool solves all inter-tool dependency problems Who would be willing to maintain this? one „box“ per tool: one PHAR for each tool solves all inter-tool dependency problems easy to maintain and update with the right tool does not (easily) allow extending tools with other Composer packages (e.g. PHPStan)
or have it in the image plan automating update of PHARS/tools that are not (yet) PHIVE-controlled Symfony security checker, Deployer, CacheTool use Composer for tools that need extensions Things to plan for automation
simple as long as possible.) 2. Then the first dependency conflict happens. 3. Move all tools to PHIVE. 4. Keep using Composer for tools that a) are not available via PHIVE b) need other Composer-installed libraries (e.g., PHPStan) Recommendation for an approach