I have multiple git-trees for my Julia installations, one for each "major" (i.e. semver minor) version that I'm interested in (currently running 0.3.x and 0.4.x, but not worrying about 0.5-dev until it stabilizes a little...). This works well; I only need to rebuild large dependencies whenever they actually update in one of the branches, which isn't very often. I've found this works well, although it's admittedly a bit space-consuming.
// T On Wednesday, October 14, 2015 at 4:54:16 PM UTC+2, milktrader wrote: > > I like this solution and I've been using git from the beginning until I > decided I needed to have multiple versions of Julia around at the same > time, with the ability to open each version whenever I choose. > > My still rough implementation of this is to rename *julia* to other names > based on version numbers > > [julia (master)] > ✈ chefs > > 0.3.11 ..... kevin > 0.4-rc1 ..... wanda > 0.4-rc4 ..... frida > 0.4-0 ..... julius > > So this is straightforward to do the hard way (which is how I'm doing it > now) by simply building each julia version from scratch. > > How would this work with using git versus tar files? > > On Wednesday, October 14, 2015 at 10:37:06 AM UTC-4, Tero Frondelius wrote: >> >> git clone https://github.com/JuliaLang/julia.git >> cd julia >> make >> >> >> after update in julia folder: >> git fetch >> git branch v0.4.1 >> make >> >> >> Maybe some fine tuning in commands, but basically drop the method of >> downloading tar and start using git. >> >> >> >> On Wednesday, October 14, 2015 at 5:21:36 PM UTC+3, milktrader wrote: >>> >>> I'm downloading full tar files for each new Julia version and of course >>> it comes with LLVM. I'd like to avoid building LLVM every single time and >>> have it compiled once, and available for all the new Julia releases (that >>> use that LLVM version of course). >>> >>> Any pointers? >>> >>> Dan >>> >>
