installation mungs dynamic vars $*PROGRAM and $*PROGRAM-NAME about ecosystem

[zoffixznet]

Given the docs for the two variables:

$*PROGRAM-NAME	Path to the current executable as it was entered on the command line, or C<-e> if perl was invoked with the -e flag.
$*PROGRAM	Location (in the form of an C<IO::Path> object) of the Perl program being executed.

Wouldn't your proposal break all possible usefulness of these variables, save displaying a name to a human? For example say "This program has {+$*PROGRAM.lines} of code in it" will error out with file not found error.

[jonathanstowe]

I guess this is somewhat complicated by the original script (which is installed with the hashed name,) being executed by a wrapper which is installed with the original name.

The script is run by the wrapper with something like:

 exit run($*EXECUTABLE, @binaries[0].hash.<files><bin/originalname>, @*ARGS).exitcode

Where @binaries is the result of searching for matching distributions.

So as far as everything is concerned when it gets to run the original script the installed hashed name is the program name.

I guess the wrapper could set an environment variable with the original name of the script which could then be used by USAGE if set, or even set some further dynvar (such as $*ORIGINAL-PROGRAM-NAME, but I agree you probably don't want to be changing the $*PROGRAM or $*PROGRAM-NAME for the reasons stated.

[zoffixznet]

which could then be used by USAGE if set

Pretty sure the USAGE is already fixed to display a friendly name

[jonathanstowe]

Ah yes, so it is, but it's done by setting an environment variable in the wrapper so for anything installed before that changed it won't be there :-\ I do have a plan to move more of the actual code of the wrapper into Compunit::Respository so it's easier to take advantage of these kind of changes, but obviously that won't help in this case :)

[jonathanstowe]

@tbrowder in this case I think it's upgrade your Rakudo if you didn't already and then reinstall the distribution that provides the script with --force - that should get you the fixed wrapper :)

[tbrowder]

Okay, I wasn't aware of those changes, and I just updated my rakudo to latest nom branch a few days ago. So that is a reinstall of zef with --force?

ALso, "$?USAGE" seems not to be defined unless you define a MAIN sub.

[JJ]

Ping?

[zoffixznet]

This issue has been resolved in rakudo awhile back.