With regard to 'built and installed' – yes, it is. But the purpose of
rakudobrew is to build and install many different versions of rakudo and switch
between them. The way it implements the task is by installing rakudo in a
location which is normally not accessible and then provide means to act
Vadim,
Your response is like a whisper in a storm. Perhaps there is meaning to
it, but I have not the ears wherewith to hear it.
(a) I am trying to find a way to test a Module under Windows when I do
not have access to a Windows machine. So no I do not see how I could
follow the steps of the
Did you ever tried to follow the steps of you script manually? I guess on a
clean system without pre-installed rakudo you'd get the same result. Because
`build` only builds a release. When it's ready one needs to `switch` to the
built. So, no, these two are different.
Best regards,
Vadim Belma
Is the appveyor stanza (see the rakudobrew script below)
- rakudobrew build moar %TEST_MOAR%
the same as what you are suggesting?
Richard
On 13/06/2020 02:53, Vadim Belman wrote:
Not really sure about it, but don't you have to do 'rakudobrew switch
moar-%TEST_MOAR%' after building? rakudob
Not really sure about it, but don't you have to do 'rakudobrew switch
moar-%TEST_MOAR%' after building? rakudobrew doesn't immediately activates a
build.
Best regards,
Vadim Belman
> On Jun 12, 2020, at 4:03 PM, Richard Hainsworth
> wrote:
>
> I have tried two different strategies on appvey
I have tried two different strategies on appveyor. (I also run a travis
test for the same Module that passes without a problem).
a) Copying from OpenSSL, which uses rakudo.git (see script below)
b) Copying from GTK::Simple, which uses Rakudobrew (see below)
Both failed for reasons I can't work
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
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 wrote:
>
> I ran into this error using Rakudobrew on appveyor (see after )
>
> I'm new at using appveyor, so maybe my script is wron
