New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use "#!/usr/bin/env rakudo" instead of perl6 in module scripts #4358
Conversation
Is #3716 related? |
Sort of. But I think that systems that haven't got /usr/bin/env and only provide /bin/env are non-standard even if no standard defines the exact location. I wouldn't add complex code that supports both /usr/bin/env and /bin/env. Better don't use the env command at all und use the configured prefix to set the interpreter to #!/usr/bin/rakudo, for example. That would also make package tools like rpmbuild and rpmlint happy. But my pull request isn't about the use of the env command. It just replaces perl6 by rakudo. |
Ah. Thanks for the explanation! Looking good. Do you have permissions to merge this yourself? |
I do wonder if it should have been |
I think at this stage, where the status of the CompUnit modules is still a bit in question (is it implementation specific or not?), that |
I thought quite a lot of aspects of the |
Ah, indeed. Hmmm... |
I did just take a glance through the tests, and I think |
|
As far as I can see there's no need to put "#!/usr/bin/env perl6" any longer into scripts like cro and zef when these modules are built and installed with recent Rakudo versions. This pull request replaces perl6 with rakudo, perl6-m with rakudo-m etc. in src/core.c/CompUnit/Repository/Installation.pm6.
BTW, if scripts use #!/usr/bin/env the package tool rpmbuild adds automatic dependencies on the package coreutils, which provides /usr/bin/env, instead of rakudo. But that's another issue that I handle in the RPM spec file.