Closed FrankGiesecke closed 2 years ago
The plugin itself does very little there: https://github.com/bamarni/composer-bin-plugin/blob/master/src/BinCommand.php#L115
so the first thing I would investigate is how COMPOSER_CACHE_DIR
is passed if it's correctly inherited by ComposerApplication
. I can't have a look at it before a while though
@FrankGiesecke as per #116 everything looks fine here: the bin plugin may only change the bin directory and nothing else.
I did notice however that if COMPOSER_CACHE_DIR
points to a relative path, then the resolved path will not be the same when executed from the root than to a namespace as the environment variables are re-evaluated.
as per https://github.com/bamarni/composer-bin-plugin/pull/116 everything looks fine here: the bin plugin may only change the bin directory and nothing else.
That's good and I can confirm that this also works in real live.
@FrankGiesecke as per https://github.com/bamarni/composer-bin-plugin/pull/116 everything looks fine here: the bin plugin may only change the bin directory and nothing else.
I did notice however that if COMPOSER_CACHE_DIR points to a relative path, then the resolved path will not be the same when executed from the root than to a namespace as the environment variables are re-evaluated.
Thats good to know. I'll check my pipelines for this and give you a feedback.
We have configured a special cache directory using the environment variable
COMPOSER_CACHE_DIR
.When running
composer install
, the cache dir is used by composer.But all packages installed by the composer-bin-plugin are always downloaded from their origin.
Why is the configured cache dir ignored?