Rackup provision for generated scripts (?) (``racket-launcher-names``)

Questions & Answers
,
1

In a given info.rkt, I am making use of racket-launcher-names which creates a launching script within the current racket installation's bin/ directory. This means that if that directory is in the current PATH, the generated program launches without first having to locate it.

Unless I am not getting something, I think that rackup does not redirect each installation's bin/...which means that when you switch to a different racket version, you also need to manually redirect the bin/.

Is it possible for rackup, to also redirect a single path added to the system PATH variable along with the rest of rackup initialisation that gets added to the rc script? The libexec/rackup-shim intercepts a call and redirects it. Would it be possible to also have a symbolic link redirecting a single directory to the right bin/ as part of rackup switch?

Or...could I achieve this with existing functionality?

2

The idea is that rackup reshim should pick up on the launcher names you added.

3

Thank you very much that worked.

The racket executables worked right from the beginning, but the package that installs the program I am talking about was created after the migration process from the 9.1 racket version and it did not work "automatically".

In a standalone installation, the launcher-names are created in ~/.local/share/racket/<version>/bin (while racket itself can be installed anywhere on the file system).

Since the racket executables worked, I did not even think that my problem could be with the shims.

All the best