-
Notifications
You must be signed in to change notification settings - Fork 85
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
Host crate on Cargo: tag julia
as binary name for julialauncher
#639
Conversation
- Note that `julialauncher` will still appear in the `bin` folder
@davidanthoff it might be worth adding https://github.com/marketplace/actions/publish-crates to automatically publish new updates to the |
julia
as binary name for julialauncher
julia
as binary name for julialauncher
If some of the deployments need to avoid installing the @davidanthoff should I add this as an option anywhere? |
Great! The whole CI workflow is very, very complicated, so probably easiest if I push to this branch to get that into working shape. Thanks so much for the start, though! |
Just a quick question. Wouldn't it be better to just rename |
For the binaries that we ship via any of the other installers the current design has the benefit that one can distinguish between the launcher process and an actual Julia process in things like the task manager. But I think with this PR here we can keep the Juliaup |
This reverts commit 336dc9a.
All done now: https://crates.io/crates/juliaup/. New package versions should be automatically pushed whenever we release a build to the release channel. Thanks, @MilesCranmer! |
This creates
julia
as another executable forjulialauncher
in the cargo bin folder. Thus allowing you to installjuliaup
from crates.io and have a workingjulia
command.Fixes #618. Note that
julialauncher
will still appear in thebin
folder.You can test this out by running:
and verifying that
juliaup
andjulia
are installed in the cargo binary folder.@davidanthoff feel free to push to this PR