RFC: composer 2 compatibility

[c33s]

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.

• no additional test cases added.
• manually tested with composer 1.10.16 and 2.0.3

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",
    }
}

[Berdir]

FWIW, this is the same approach that for example https://github.com/zaporylie/composer-drupal-optimizations/pull/17 chose as well, which has worked well there, so +1.

[Tobion]

Duplicate of #223 which has been declined

[c33s]

Duplicate of #223 which has been declined

still required for an easy transition from composer1 to composer2

ci's break because of this

[kubawerlos]

ci's break because of this

Yes, but @hirak said he won't release a new version. composer self-update --2 is the best workaround I guess.

[c33s]

Yes, but @hirak said he won't release a new version.

one more version is not that difficult or cumbersome.

composer self-update --2 is the best workaround I guess.

this is no workaround for multi environments (composer1 and composer2) see also the comment of @vworldat https://github.com/hirak/prestissimo/issues/233#issuecomment-720436440

[kubawerlos]

one more version is not that difficult or cumbersome.

You don't have to convince me, after all, I made https://github.com/hirak/prestissimo/pull/223

this is no workaround for multi environments

Well, I managed with the help of composer self-update --1/composer self-update --2 to handle such situation, not perfect, but woroking.