-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use Bloop fork, default to 100% domain sockets for Bloop communication #469
Conversation
79474e2
to
9707468
Compare
|
How come this is necessary? We have control over bloop. We can upstream the necessary changes there, if required. |
https://github.com/oyvindberg/bleep , but I don't think anyone's using blaap or bluup |
FYI, the fork of Bloop (called bleep for now) lives here. The name collision with https://github.com/oyvindberg/bleep is unfortunate, but scala-cli/bleep might be temporary. Some of the motivations to work from it rather than from upstream Bloop are
It's 100% my own personal initiative for now. We (VirtusLab) might soon come up with plans to ease the maintenance of Bloop, and hopefully make this fork unnecessary. |
9707468
to
4ae93ca
Compare
488264c
to
4a2d12a
Compare
f4a1e87
to
4b61568
Compare
afcdccb
to
208536f
Compare
So that we can go 100% domain sockets.
So that we can still download the launchers via the GitHub actions UI if ever docker image building fails.
5ad9470
to
bd768a6
Compare
No description provided.