You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are a few nails in the coffin for composer global based install:
Phar works well already and is the preferred method of install today.
Supporting both phar installation and composer based installation causes pain in dealing with dependencies.
Installing with composer global can lead to dependency collisions with other globally installed tools
The steps we need to take to get rid of phar as I see it are:
Add phar CI actions. We do run tests on the composer repo but I think we need to do at least some testing on the built phar before drafting a release or merging a pull.
Remove concrete5/console from packagist.org, or update it in a way that makes it obvious that someone should install using phar
The text was updated successfully, but these errors were encountered:
There are a few nails in the coffin for composer global based install:
The steps we need to take to get rid of phar as I see it are:
The text was updated successfully, but these errors were encountered: