Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Check Arch Linux installer works before release

See original GitHub issue

As we’re getting ready for the release, I’d like to make sure there are no breakages with our existing installation methods. @TheElectronWill Could you check that running sbt install produces a valid Arch Linux package that you can install in your box? I can’t do that because I no longer own an Arch Linux box.

Issue Analytics

State:
Created 3 years ago
Comments:9 (8 by maintainers)

Top GitHub Comments

1reaction

jvicancommented, May 7, 2020

I’ll remove the creation of the /usr/lib/bloop folder as well as the symlink, thanks!

Keep in mind that you should not be compiling to GraalVM during the installation process, we compile to GraalVM native in CI/CD during the install step that generates all of the formulas and binaries. Could you try the installation doing sbt install instead of sbt createLocalArchPackage?

1reaction

TheElectronWillcommented, May 7, 2020

First problem fixed by installing graalvm and graalvm-native-image (of course! should have thought of that earlier…). But 8 gigs of RAM don’t seem to be enough to complete the building of the native image so I can’t test any further 🙁

we no longer have symlinks nor the previous installation structure, now we only install a binary in /usr/bin/bloop and that’s it.

The current PKGBUILD creates a folder /usr/lib/bloop, then a link to the executable within it. If we don’t need the folder anymore (I see that .jvmopts should now go into $HOME/.bloop/.jvmopts or in bloop.json) it should be removed.