I'm still using rakudobrew for myself, it is not a problem. Besides, we still install perl6.
What I'd look for is if correct PATH is setup; and check if rakudobrew is been used properly. Note that different modes (env or shim) would need different handling. To my understanding, in a container shims are preferable over env. Best regards, Vadim Belman > On Jun 12, 2020, at 2:40 PM, Elizabeth Mattijsen <l...@dijkmat.nl> wrote: > > It is my understanding that rakudobrew has been renamed to rakubrew: > https://rakubrew.org Could the be the issue? > >> On 12 Jun 2020, at 14:59, Richard Hainsworth <rnhainswo...@gmail.com> wrote: >> >> I ran into this error using Rakudobrew on appveyor (see after <snip>) >> >> I'm new at using appveyor, so maybe my script is wrong. But I wonder whether >> its because of a name change to raku without a backward alias to perl6. >> >> <snip> >> >> Rakudo has been built and installed. >> >> Updating shims >> Done, moar-2020.05.1 built >> rakudobrew build zef >> Cloning into 'zef'... >> Your branch is up to date with 'origin/master'. >> rakudobrew: perl6: command not found >> Command exited with code 1 >
