Skip to content
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

Phase out composer global based install in favor of Phar #25

Open
2 tasks
KorvinSzanto opened this issue Sep 24, 2021 · 0 comments
Open
2 tasks

Phase out composer global based install in favor of Phar #25

KorvinSzanto opened this issue Sep 24, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@KorvinSzanto
Copy link
Member

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
@KorvinSzanto KorvinSzanto added the enhancement New feature or request label Sep 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant