Ubuntu/Debian package installation not included in the instructions

[JJ]

You will need to install make and gcc to make this work. This is probably installed almost everywhere nowadays, but I was just trying to use this in a bare-bones VPS and it was not. It's also using git, so you might want to warn about that too.
Additionally, maybe include a simple detection of needed programs in the script, so that ugly errors don't show up. I can do that myself.

[patrickbkr]

download works fine without any of those. So a check must only happen, when build is actually used.

For the build command only git and perl are needed unconditionally. Those are already checked here.

gcc is not needed when building on JVM or when building with clang. make is highly platform dependent (nmake, gmake, make are all possibilities). All of these are already checked by the Configure.pl of Rakudo itself (not as pretty as it could, but it does the checking). Thus I opted to not try to reproduce the checks in Rakubrew. This means less duplication and less potential for running out of sync. Also reproducing the logic in Rakubrew is bound to be very fragile, as the actual requirements are dependent on the options passed to Configure.pl and other factors such as which programs are first found in PATH.

If one desires to have prettier error messages, I'd favour that we improve them in Rakudos Configure.pl than trying to reproduce the logic in Configure.pl in Rakubrew.

[JJ]

For some reason, that didn't happen. I will probably need to find out why... El sáb., 12 jun. 2021 21:11, Patrick Böker ***@***.***> escribió:

…

download works fine without any of those. So a check must only happen, when build is actually used. For the build command only git and perl are needed unconditionally. Those are already checked here <https://github.com/Raku/App-Rakubrew/blob/master/lib/App/Rakubrew/Build.pm#L227> . gcc is not needed when building on JVM or when building with clang. make is highly platform dependent (nmake, gmake, make are all possibilities). All of these are already checked by the Configure.pl of Rakudo itself (not as pretty as it could, but it does the checking). Thus I opted to not try to reproduce the checks in Rakubrew. This means less duplication and less potential for running out of sync. Also reproducing the logic in Rakubrew is bound to be very fragile, as the actual requirements are dependent on the options passed to Configure.pl and other factors such as which programs are first found in PATH. If one desires to have prettier error messages, I'd favour that we improve them in Rakudos Configure.pl than trying to reproduce the logic in Configure.pl in Rakubrew. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#15 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAAD5FDW6ODA6TEOAMKQ5DTSOWPNANCNFSM46S62PPQ> .

[patrickbkr]

@JJ Did you manage to do some digging into why this failed for you?

[JJ]

I would probably need to dig up a different VM with similar characteristics to do it, since it's already installed into the VPS...