-
Notifications
You must be signed in to change notification settings - Fork 326
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
Avoid name duplication of the enso
universal launcher
#10476
Comments
I've just downloaded the latest nightly and it contains the
the executable seems to work to some extend. I can |
I have downloaded the Windows bundle. Seems to work OK to me. I've checked most of the functionality, incl. the installation feature and all seem to work as expected. I have only not checked the self-upgrade. I will be starting using |
There are two executables named
enso
among the daily bits we produce. That's confusing and we shall fix it.One of them is called Enso launcher. To learn about it, please visit our download page: https://github.com/enso-org/enso/releases/tag/2024.1.1 - the download is in section called Enso Engine on that page, but in fact, it is not the engine, it is the launcher!
To learn more abou tthe enso launcher visit this documentation page - it contains nice description of the whole universtal launcher/updater picture...
However to benefit from the work done by
we need to find a better location for exposing native image built launcher. The idea is to rename the launcher to
ensoup
:It is a nice, illustrative name derived from the
rustup
example that nicely describes one of the purposes ofensoup
- download the distributions of Enso automatically. Once theenso
in the bundle is renamed toensoup
, we can proceed with placing a native image built binary next to it under the nameenso
- but that's for a different PR.The text was updated successfully, but these errors were encountered: