Of course it is not a problem, but now it is less flexible because I had to define the application's name in configuration file.
1) If $0 is wrong, its a bug/deficiency in cava packager, submit a bug report
2) usually registry entries are handled by installer programs
3) This is a flexible workaround
$ cat myregular.pl
use MySuperApp;
MySuperApp->run;
$ cat mypackedapp.pl
BEGIN {
use Cava::Pack;
$0 = $Cava::Pack::EXEPATH;
}
use MySuperApp;
MySuperApp->run;
|