how a designated command name, 'compile-r7rs' would go with the conventional

"make & make install" way.  If multiple implementations provide compile-r7rs command

and a user wants to install them in standard location (e.g. /usr/bin, /usr/local/bin etc.),

there will be a conflict.

The c99 command has the same problem but I guess it's less of a problem since there

are not many popular C compilers, and these days people usually installs binaries with

some package managers, which take care of the conflict (e.g. alternative mechanism

on Debian).   In Scheme, we have lots of implementations and it's typical that a user

installs them by herself.

I'm old school and get used to have compiler command name configurable in

Makefile, so I don't see the need of fixing compiler command name.

(Script interpreter name is slightly different, for it directly affects distribution

of ready-to-run Scheme scripts.  For the compilers, though, users will

have build step and the build tool can take care of multiple selections.)

Maybe the convention has changed---e.g. is it now common that installs

everything in per-implementation subdirectory instead of scattering them

in $exec_prefix/bin, $exec_prefix/lib etc?  Then each implementation

doesn't need to worry about stepping on each other and just let the

higher layer of the system to do the selection.  Does this srfi presume

such convention?