Package: jill
JILL.pyThe enhanced Python fork ofJILL-- Julia Installer for Linux (and every other platform) -- LightFeaturesdownload Julia releases from thenearestmirror serversupport all platforms and architecturesmanage multiple julia releaseseasy-to-use CLI toolInstall JILLFor the first time users ofjill, you will need to install it usingpip:pip install jill --user -U. Also use this to upgrade JILL version.Python >= 3.6is required. For base docker images, you also need to make surewgetandgnupgare installed.Installing JuliasWhen you typejill install, it does the following things:query the latest versiondownload, verify, and install juliamake symlinks, e.g.,julia,julia-1,julia-1.6For common Julia users:Get the latest stable release:jill installGet the latest 1.y.z release:jill install 1Get the latest 1.6.z release:jill install 1.6Get the specific version:jill install 1.6.2,jill install 1.7.0-beta3Get the latest release (including unstable ones):jill install --unstableNote that for Julia 1.10, you'll have to install it withjill install '"1.10"'because of thepython-fire limit.For Julia developers and maintainers:Get the nightly builds:jill install latest. This gives youjulia-latest.Checkout CI build artifacts of specific commit in theJulia Repository:jill install 1.8.0+cc4be25c(<major>.<minor>.<patch>+<build>with at least the first 7 characters of the
hash). This gives youjulia-dev.Some flags that can be useful:No confirmation before installation:jill install --confirmDownload from Official source:jill install --upstream OfficialKeep downloaded contents after installation:jill install --keep_downloadsForce a reinstallation:jill install --reinstallThe symlinksTo start Julia, you can use predefined JILL symlinks such asjulia.jill installuses the following rule makes sure
that you're always using the latest stable release.Stable releases:juliapoints to the latest Julia release.julia-1points to the latest 1.y.z Julia release.julia-1.6points to the latest 1.6.z Julia release.For unstable releases such as1.7.0-beta3, installing it viajill install 1.7 --unstableorjill install 1.7.0-beta3will only give youjulia-1.7; it won't make symlinks forjuliaorjulia-1.To dance on edge:julia-latestpoints to the nightly build fromjill install latestjulia-devpoints to the julia CI build artifacts from, for example,jill install 1.8.0+cc4be25c.List symlinks and their target versionsjill list [version]gives you every symlinks and their target Julia versions.Change symlink targetFor non-windows system, you are free to uselncommand to change the symlink targets. For Windows
it uses an entry.cmdfile for this so you'll need to copy them. In the meantime,jill switchprovides a simple and unified way to do this:jill switch 1.6: letjuliapoints to the latest julia 1.6.z release.jill switch <path/to/my/own/julia/executable>: letjuliapoints to custom executables.jill switch 1.6 --target julia-1: letjulia-1points to the latest julia 1.6.z release.About downloading upstreamsBy default, JILL tries to be smart and will download contents from thenearestupstream. You can
get the information of all upstreams viajill upstream. Here's what I get in my laptop, I live in
China so the official upstreams aren't so accessible for me :(To temporarily disable this feature, you can use flag--upstream <server_name>. For instance,jill install --upstream Officialwill faithfully download from the official julialang s3 bucket.To permanently disable this feature, you can set environment variableJILL_UPSTREAM.Note that flag is of higher priority than environment variable. For example, ifJILL_UPSTREAMis
set to mirror server"TUNA", you can still download from the official source viajill install --upstream Official.About installation and symlink directoriesHere's the default JILL installation and symlink directories:systeminstallation directorysymlink directorymacOS/Applications~/.local/binLinux/FreeBSD~/packages/julias~/.local/binWindows~\AppData\Local\julias~\AppData\Local\julias\binFor example, on Linuxjill install 1.6.2will have a julia folder in~/packages/julias/julia-1.6and symlinksjulia/julia-1/julia-1.6created in~/.local/bin.Particularly, if you're usingjillasrootuser, you will do a system-wide installation:Installation directory will be/opt/juliasfor Linux/FreeBSD.Symlink directory will be/usr/local/binfor Linux/FreeBSD/macOS.To change the default JILL installation and symlink directories, you can set environment variablesJILL_INSTALL_DIRandJILL_SYMLINK_DIR.(Deprecated)jill installalso provides two flag--install_dir <dirpath>and--symlink_dir <dirpath>, they have higher priority than the environment variablesJILL_INSTALL_DIRandJILL_SYMLINK_DIR.JILL environment variablesjillis made as a convenient tool and it can sometimes be annoying passing flags to it. There are
some predefined environment variables that you can use to set the default values:Specify a default downloading upstreamJILL_UPSTREAM:--upstreamOverride default symlink directoryJILL_SYMLINK_DIR:--symlink_dirOverride default installation directoryJILL_INSTALL_DIR:--install_dirThe flag version has higher priority than the environment variable version.Advanced: Example with cronIf you're tired of seeing(xx days old master)in your nightly build version, thenjillcan
make your nightly build always the latest version usingcron:# /etc/cron.d/jillPATH=/usr/local/bin:/usr/sbin:/usr/sbin:/usr/bin:/sbin:/bin# install a fresh nightly build every day*0***rootjillinstalllatest--confirm--upstreamOfficialAdvanced: Registering a new public releases upstreamIf it's an public mirror and you want to share it worldwide to other users of JILL. You can add an
entry to thepublic registry, make a PR, then I will tag a new release
for that.Please checkthesources.jsonformatfor more detailed information on the
format.Advanced: Specifying custom (private) downloading upstreamTo add new private upstream, you can create a file~/.config/jill/sources.json(fow Windows it is~/AppData/Local/julias/sources.json) and add your own upstream configuration just like the JILLsources.jsondoes. Once this is done JILL will recognize this new
upstream entry.Please checkthesources.jsonformatfor more detailed information on the
format.Advanced: make a Julia release mirrorThere are two ways to do so:useaws s3 sync, this should be the easiest way to do so I highly recommend this.(Deprecated)usejill mirrorcommand withmirror config example. I
didn't know about theaws s3 syncstuff when I implemented this.The Julia release mirror does not contain Julia package contents, to mirror all the Julia packages
and artifacts (which requires >1.5Tb storage), you can useStorageMirrorServer.jl.Advanced: The Python APIjill.pyalso provides a set of Python API:fromjill.installimportinstall_juliafromjill.downloadimportdownload_package# equivalent to `jill install --confirm`install_julia(confirm=True)# equivalent to `jill download`download_package()You can read its docstring (e.g.,?install_julia) for more information.FAQsWhy you should use JILL?Distro package managers (e.g.,apt,pac) is likely to provide a broken Julia with incorrect
binary dependencies (e.g., LLVM ) versions. Hence it's recommended to download and extract the
Julia binary provided inJulia Downloads.jill.pydoesn't do
anything magical, but just makes such operation even stupid.Why I make the python fork of JILL?At first I found myself needing a simple tool to download and install Julia on my macbook and
servers in our lab, I made my own shell scripts and I'd like to share it with others. Then I found
thejill.shproject, Abel knows a lot shell so I decide to contribute my macOS Julia
installer tojill.sh.There are three main reasons for why I decided to start my Python fork:I live in China. Downloading resources from GitHub and AWS s3 buckets is a painful experience.
Thus I want to support downloading from mirror servers. Adding mirror server support to jill.sh is
quite complicated and can easily become a maintenance nightmare.I want to make a cross platform installer that everyone can use, not just Linux/macOS users. Shell
scripts doesn't allow this as far as I can tell. In contrast, Python allows this.Most importantly, back to when I start this project, I knew very little shell, I knew nothing
about C/C++/Rust/Go and whatever you think a good solution is. I happen to knew a few Python.For some "obvious" reason, Julia People don't like Python and I understand it. (I also don't like
Python after being advanced Julia user for more than 3 years) But to be honest, revisiting this
project, I find using Python is one of the best-made decision during the entire project. Here is the
reason: no matter how you enjoy Julia (or C++, Rust), Python is one of the best successful
programming language for sever maintenance purpose. Users can easily found tons of "how-to"
solutions about Python and it's easy to write, deploy, and ship Python codes to the world via PyPI.And again, I live in China so I want to rely on services that are easily accessible in China, PyPI
is, GitHub and AWS S3 bucket aren't. A recent Julia installer projectjuliaupwritten in Rust
solves the Python dependency problem very well, but the tradeoff is thatjuliaupneeds its own
distributing system (currently GitHub and S3 bucket) to make sure it can be reliably downloaded to
user machine. And for this it just won't be as good as PyPI in the foreseeable future.Is it safe to usejill.py?Yes,jill.pyuse GPG to check every tarballs after downloading. Also,*.dmg/*.pkgfor macOS
and.exefor Windows are already signed.What's the difference betweenjill.shandjill.pyjill.shis a shell script that works quite well on Linux x86/x64 machines.jill.pyis
an enhanced python package that focus on Julia installation and version management, and brings a
unified user experience on all platforms.Whyjuliafails to startThe symlinkjuliaare stored inJILL predefined symlinks
dirthus you have to make sure this folder is inPATH. Search "how to add folder to PATH on xxx system" you will get a lot of solutions.How do I use multiple patches releases (e.g.,1.6.1and1.6.2)Generally, you should not care about patch version differences sojill.pymake it explicitly that
only one of 1.6.x can exist. If you insist to have multiple patch versions, you could usejill install --install_dir <some_other_folder>to install Julia in other folder, and then manually make
a symlink back. As I just said, in most cases, common users should not care about this patch version
difference and should just use the latest patch release.How to only download contents without installation?Usejill download [version] [--sys <system>] [--arch <arch>]. Checkjill download --helpfor
more details.Linux with musl libcFor Julia (>= 1.5.0) in Linux with musl libc, you can just dojill installand it gives you the
right Julia binary. To download the musl libc binary usingjill download, you will need to pass--sys muslflag.MacOS with Apple silicon (M1)Yes it's supported. Because macOS ARM version is still of tier-3 support, jill.py will by default
install the x86_64 version. If you want to use the ARM version, you can install it viajill install --preferred-arch arm64.CERTIFICATE_VERIFY_FAILED errorIf you're confident, tryjill install --bypass-ssl.Skip symbolic links generationIf for some reason you prefer to download julia without generating symbolic linksjill install --skip-symlinks