#!/usr/bin/env perl6
is probably better let /usr/bin/env find the path to perl6
On 01/04/17 17:16, ToddAndMargo wrote:
Hi All,
Scientific Linux 7.3 (RHEL clone)
I just came out of a panic with EPEL and their release update
of Rakudo. Hosed the hole thing. Total mess.
Anyway, thanks to the guys at the IRC channel, after a lot
of uninstalling and erasing, I am now on
https://github.com/nxadm/rakudo-pkg/releases
https://github.com/nxadm/rakudo-pkg/releases/download/2017.03_02/perl6-rakudo-moarvm-CentOS7.3.1611-20170300-02.x86_64.rpm
Problem, EPEL and `nxadm` put `perl6` in different places:
EPEL: /usr/bin/perl6
nxadm: /opt/rakudo/bin/perl6
and all my Linux Perl6 programs start with
#!/usr/bin/perl6
The following cured the issue
# ln -s /opt/rakudo/bin/perl6 /usr/bin/perl6
I reported the issue over on
https://github.com/nxadm/rakudo-pkg/issues/9
Therefore, I would like best practice advice:
If various releases of Linux's rakudo are going to install in
different places and I want Linux cross machine compatibility,
is it best to leave the `#!/usr/bin/perl6`off and run everything
the hard way with `perl6 xxx.pl6` and remove the bash first
line path?
I don't suppose there is a way to dual path the first line?
Your thoughts on the issue?
Many thanks,
-T
--
.~. In my life God comes first....
/V\ but Linux is pretty high after that :-D
/( )\ Francis (Grizzly) Smit
^^-^^ http://www.smit.id.au/
