On 11/28/13, Moritz Lenz <mor...@faui2k3.org> wrote: > > On 11/28/2013 10:32 PM, Parrot Raiser wrote: >> Is there some reason that 2013.11 changed the name of perl6 to >> perl6-p? It broke my download-compile-and-set-links script. > > Yes, the possibility to run Rakudo on multiple backends. > > If my memory doesn't deceive me, you were even one of those who asked > for a rename to avoid naming collisions, no? > Not I, AFAIR. (Of course, it could be the onset of dementia. :-)* )
> That said, the install process should still create a 'perl6' (or > perl6.bat/perl6.exe on windows) binary/script for you. > Actually, a plethora of perl6/perl6-p. (All different, according to the inodes.) 20624470 -rwxr-xr-x 1 u u 51414 2013-11-25 18:15 rakudo-star-2013.11/perl6-p 20624426 -rwxr-xr-x 1 u u 51414 2013-11-25 17:54 rakudo-star-2013.11/rakudo/perl6-p 20624464 -rwxr-xr-x 1 u u 51414 2013-11-25 18:15 rakudo-star-2013.11/rakudo/perl6 10264609 -rwxr-xr-x 1 u u 51414 2013-11-25 18:15 rakudo-star-2013.11/install/bin/perl6 Plus some directories that appear relevant to Parrot and the JVM. If I want the script to link reliably to the right executable for Parrot, which should I select?
