#qa follow up: a major version number change usually implies a BC change. What changes will users have to make to their composer.json in order to use composer 2?
#qa follow up: a major version number change usually implies a BC change. What changes will users have to make to their composer.json in order to use composer 2?
composer 1.10 outputs a lot of 'deprecated, will be broken in 2' for our core composer.json :(
#qa what do you think about adding repositories-dev section in composer.json? it would make local development of several packages more easier: - in dev you can specify path for package - in usual repo could be real repository
#qa have you tried PHIVE? It helps to install and verify phar dependencies https://github.com/phar-io In affirmative case, what do you think about it? 🙂
#qa feeadback: i have been using PHP for 20 years and composer is one of the best thing which has happened in the ecosystem and it is kind of enabler for others like frameworks