Composer detection problem if composer is wrapped in a shell script

[c33s]

os: debian12
symfony: 5.8.6
composer: 2.6.6

my composer file is a shell script which is doing different stuff for me before actually running composer. so i there is the bash script /usr/local/bin/composer which runs the actual composer file /usr/local/bin/composer-bin

shouldn't a simple detection be enough?

command -v composer
/usr/local/bin/composer

which composer
/usr/local/bin/composer

[tucksaun]

shouldn't a simple detection be enough?

unfortunately no as we might need to change PHP version or settings before running composer. to do so we need to "basically" run php ... /usr/local/bin/composer which is not possible with a shell wrapper.

we do have support for php wrappers though so if your script starts with #!/usr/bin/env php it will work.

[c33s]

sadly it is a bash script and has to be a bash script, it would also feel wrong to translate a bash script which is running regular shell commands to php and having a lot of exec function calls. i assume it won't work if it is a bash script, will it?

would it be possible to add a environment variable which sets the composer path so that symfony-cli is not trying to detect it? or is there any other workaround so that symfony-cli is not working around my script?