question-mark
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.

Add `coursier install bloop` as the recommended installation

See original GitHub issue

The next bloop release will be mainly installed via coursier, instead of forcing clients to either run the generic curl script or install bloop via a dependency manager. The brew, Scoop and Linux distros installation formulas/recipes will be changed to use coursier install to install bloop. The only reason why somebody would install bloop this way instead of via a manual coursier install would be to install also bash/zsh autocompletions.

Right now I’m investigating what changes we need, so all of this is still being considered and there’s no final decision. I’ve also made a comment in https://github.com/coursier/apps/pull/8 to ask if coursier install can deal with the fact that we don’t have native binaries for Windows.

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:7
  • Comments:5 (3 by maintainers)

github_iconTop GitHub Comments

4reactions
jvicancommented, Mar 28, 2020

To close this ticket and the 1.4.0 release we need the following:

  1. Native binaries need to be created in CI and published to the release.
  2. Our dependency on install.py needs to go away.
    • We will still keep the installer for a while but we will no longer use it in our official installation methods.
    • We will mark the “universal” installation method on the website as deprecated.
    • The launcher implementation needs to change to not use the install.py anymore.
  3. Our formulas will install completions and the bloop CLI. The bloop server will be launched automatically based on the version of the CLI.
  4. Formulas will no longer install systemd and brew services. We will keep them around in case people feel really strongly that they want to use them, but they will no longer be installed automatically and recommended.
2reactions
jvicancommented, Mar 30, 2020

Made good progress porting the brew formula to install our CLI directly and changing the launcher to use coursier as the only way of starting the bloop server. I will follow up with more progress updates here soon.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Bloop · Compile, test and run Scala code fast
Installation Guide · 1Do you need to install Bloop? · 2Pick your installation method · 3Set up your build · Requirements · Install...
Read more >
scalacenter/bloop - Gitter
I'm trying to install latest bloop using coursier, but unfortunately it fetches bloop v1.4.5-6-4768184c as latest available. Tried cs uninstall bloop and ...
Read more >
Installation - Coursier
The setup command installs a number of standard Scala CLI applications by default. Pass a custom list of applications to install instead with...
Read more >
Visual Studio Code | Metals - Scalameta
log to watch the build import progress. Behind the scenes, Metals uses Bloop to import sbt builds, but you don't need Bloop installed...
Read more >
Release notes | Scala CLI
Installation via Scoop on Windows​. Scala CLI can now be installed via Scoop on Windows, with a command such as. scoop install scala-cli....
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found