RFC: composer 2 compatibility #239
Conversation
|
FWIW, this is the same approach that for example zaporylie/composer-drupal-optimizations#17 chose as well, which has worked well there, so +1. |
|
Duplicate of #223 which has been declined |
still required for an easy transition from composer1 to composer2 ci's break because of this |
Yes, but @hirak said he won't release a new version. |
one more version is not that difficult or cumbersome.
this is no workaround for multi environments (composer1 and composer2) see also the comment of @vworldat #233 (comment) |
You don't have to convince me, after all, I made #223
Well, I managed with the help of |
a quick hack to allow the plugin to exist in environments where composer1 and composer2 are used. if composer2 is detected is simply deactivate itself.
i am quite sure there are better ways to archive that but i just want a quick solution for myself.
to try it out add the following to your
composer.json{ "repositories": { "prestissimo": { "type": "vcs", "url": "https://github.com/c33s/prestissimo.git" } }, "require": { "hirak/prestissimo": "dev-feature/composer2-compat", } }