# \`juliaup\` for for Mac and Linux

**URL:** <https://discourse.julialang.org/t/juliaup-for-for-mac-and-linux/66721>\
**Category:** Tooling\
**Tags:** linux, juliaup\
**Created:** [August 20, 2021, 10:17am UTC](https://discourse.julialang.org/t/juliaup-for-for-mac-and-linux/66721 "2021-08-20T10:17:43Z")\
**Posts on this page:** 9\
**Page:** 2

<div class="post-metadata">

**Author:** ![davidanthoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/davidanthoff/32/223493_2.png) [@davidanthoff](https://discourse.julialang.org/u/davidanthoff)\
**Post date:** [August 21, 2021, 4:18pm UTC](https://discourse.julialang.org/t/juliaup-for-for-mac-and-linux/66721/21 "2021-08-21T16:18:41Z")

</div>

We could actually publish `juliaup` on [creates.io](http://creates.io), and then you could directly install it with `cargo install juliaup`. But I actually think that probably doesn’t make that much sense and we should instead just finish the install script that I mentioned above.

If you want to hack on juliaup, then the steps that @ericphanson described are perfect!

---

<div class="post-metadata">

**Author:** ![SL6Trip](https://avatars.discourse-cdn.com/v4/letter/s/4da419/32.png) [@SL6Trip](https://discourse.julialang.org/u/SL6Trip)\
**Post date:** [August 22, 2021, 2:10am UTC](https://discourse.julialang.org/t/juliaup-for-for-mac-and-linux/66721/22 "2021-08-22T02:10:08Z")

</div>

The default location scoop installs programs to (which can be changed) is not in the system files directories, but the user directories eg. `C:\Users\<user>\scoop`. This avoids a lot of problems to do with `PATH` and UAC permissions, especially if you stick to the main scoop bucket. winget somewhat “supports” it, but it depends on each individual application supporting a `--location` [parameter](https://github.com/microsoft/winget-cli/issues/201) instead of having a global install location (eg. different drives).

Also winget also does not support [installing of portable applications](https://github.com/microsoft/winget-cli/issues/182), which is the main type of programs that scoop targets.

So I’m not so sure winget will make scoop redundant, at least until it manages to implement these features. I am especially skeptical about the portable applications one. To me, winget is still more focused on .exe and .msi installers as the target applications.

---

<div class="post-metadata">

**Author:** ![davidanthoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/davidanthoff/32/223493_2.png) [@davidanthoff](https://discourse.julialang.org/u/davidanthoff)\
**Post date:** [August 22, 2021, 2:45am UTC](https://discourse.julialang.org/t/juliaup-for-for-mac-and-linux/66721/23 "2021-08-22T02:45:41Z")

</div>

Ah, interesting re scoop. I think the situation for store apps is generally different because they a) always install per user and b) handle the `PATH` problem really elegantly. So at least for us `winget` should be perfect once they enable the Windows Store source and then our existing Windows Store version can just be installed with `winget`.

---

<div class="post-metadata">

**Author:** ![banksiaboy](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/banksiaboy/32/27032_2.png) [@banksiaboy](https://discourse.julialang.org/u/banksiaboy)\
**Post date:** [September 15, 2021, 3:08am UTC](https://discourse.julialang.org/t/juliaup-for-for-mac-and-linux/66721/25 "2021-09-15T03:08:30Z")

</div>

You can install pip independently. Then install Jill. On my Ubuntu system I don’t do any major Python configurations at the base system level. I do that in a python virtual environment. My base Python has always been reliable since I adopted that rule. The other good thing about Python is - I don’t program in it any longer

---

<div class="post-metadata">

**Author:** ![jling](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jling/32/212909_2.png) [@jling](https://discourse.julialang.org/u/jling)\
**Post date:** [October 15, 2024, 12:24pm UTC](https://discourse.julialang.org/t/juliaup-for-for-mac-and-linux/66721/26 "2024-10-15T12:24:49Z")

</div>

> [@davidanthoff](#):
>
> But for now `brew install juliaup` or `apt install juliaup` I think would also work.

`apt install juliaup` doesn’t work, and I can’t find anything on Ubuntu: [Ubuntu – Package Search Results -- juliaup](https://packages.ubuntu.com/search?keywords=juliaup&searchon=names&suite=noble&section=all)

(I don’t use Ubuntu at all but I got some feedback from a workshop last week that the official way to install julia via juliaup is `curl .. | sh` seems to be not ideal)

---

<div class="post-metadata">

**Author:** ![Palli](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/palli/32/3380_2.png) [@Palli](https://discourse.julialang.org/u/Palli)\
**Post date:** [October 15, 2024, 12:31pm UTC](https://discourse.julialang.org/t/juliaup-for-for-mac-and-linux/66721/27 "2024-10-15T12:31:47Z")

</div>

I don’t find it in snap either, but I do find it has latest Julia 1.11.0 though also outdated:

> **[Install julia on Linux | Snap Store](https://snapcraft.io/julia)**
>
> Get the latest version of julia for Linux - The Julia programming language

> lts/stable 1.6.7 9 October 2024

There has been talk of letting it install Juliaup, rather than Julia (and it works in more than Ubuntu, though snapd disabled in Linux Mint…).

There IS also for 64-bit Linux (not just macOS…):

> **[juliaup](https://formulae.brew.sh/formula/juliaup)**
>
> Homebrew’s package index

---

<div class="post-metadata">

**Author:** ![giordano](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/giordano/32/2166_2.png) [@giordano](https://discourse.julialang.org/u/giordano)\
**Post date:** [October 15, 2024, 1:14pm UTC](https://discourse.julialang.org/t/juliaup-for-for-mac-and-linux/66721/28 "2024-10-15T13:14:22Z")

</div>

I don’t think David was implying that `juliaup` is in Debian/Ubuntu repositories (which never was), but that hypothetically someone could try to push it there (but no one has done anything in this direction).

---

<div class="post-metadata">

**Author:** ![jling](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jling/32/212909_2.png) [@jling](https://discourse.julialang.org/u/jling)\
**Post date:** [October 15, 2024, 1:46pm UTC](https://discourse.julialang.org/t/juliaup-for-for-mac-and-linux/66721/29 "2024-10-15T13:46:03Z")

</div>

> [@davidanthoff](#):
>
> I could also imagine a future where Juliaup becomes the official, default deployment mechanism for Julia at which point commands like `brew install julia` or `sudo apt install julia` would actually install Juliaup. But for now `brew install juliaup` or `apt install juliaup` I think would also work.

To me at least, the first sentence is about what potentially could happen in the future, and the “for now” is literally for now…

But clearly I agree with the reality, I was more of asking what’s the status

---

<div class="post-metadata">

**Author:** ![tecosaur](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tecosaur/32/23206_2.png) [@tecosaur](https://discourse.julialang.org/u/tecosaur)\
**Post date:** [October 15, 2024, 2:36pm UTC](https://discourse.julialang.org/t/juliaup-for-for-mac-and-linux/66721/30 "2024-10-15T14:36:28Z")

</div>

I’m surprised to see that nobody’s linked repology yet.

> **[juliaup package versions - Repology](https://repology.org/project/juliaup/versions)**
>
> List of package versions for project juliaup in all repositories

TLDR; It’s packaged for Arch, Gentoo, Homebrew, openSUSE, Solus, and Void.

[Previous page](https://discourse.julialang.org/t/juliaup-for-for-mac-and-linux/66721.md?page=1)