The docs explain a solution for @php in composer, which will result in issues

[gisostallenberg]

What happened?

When using (at least) the docker images for latest and latest-php8.2, the docs at https://frankenphp.dev/docs/known-issues/#composer-scripts-referencing-php suggest adding a script at /usr/local/bin/php, but the actual php binary is already located there. It will result in issues when running PHPStan or Rector, which try to run that PHP binary.
Not adding the solution proposed will actually work just fine (also for @php sections in composer.json, so maybe the known issues section is outdated or only targeted at other docker images.

At least a notice about this is justified in the docs, see #810

Build Type

Docker (Debian Bookworm)

Worker Mode

No

Operating System

GNU/Linux

CPU Architecture

x86_64

PHP configuration

N/A

Relevant log output

No response

[dunglas]

I'm not sure to get the problem. This workaround is relevant only if you use the built-in frankenphp php-cli sub-command. It isn't necessary if you use the classic PHP CLI.

Maybe it's not clear enough in docs?

[dunglas]

Closing for now, feel free to reopen if I misunderstood.

[gisostallenberg]

Well... I misunderstood that this is not always needed, so I added a script and put it in /usr/local/bin/php, but when having an actual php binary there, this (off course) results in errors.
So I thought to save others from doing the same stupid thing, add a warning that this is only needed in certain situations. For me that was not clear. I understood that "if there is @php in your composer.json" this should always be fixed using the script proposed.

[dunglas]

Good idea for the warning!