While not directly relevant right away, one idea that we have mulled over is the possibility of people having their own METADATA snapshots or even completely private METADATAs. This is just a thought, and there may be better ways to do this.
We have this same problem maintaining JuliaBox. 0.3 When supporting a large number of packages, invariably something breaks. At least for JuliaBox supported packages, we will probably move towards a monthly release process and try to ensure that everything works together as a whole. -viral On Monday, November 16, 2015 at 8:35:45 AM UTC+5:30, Sheehan Olver wrote: > > > I'm trying to figure out the "best" way to create a stable version of > Julia + Gadfly + PyPlot + IJulia (+ other packages?) for a semester long > course. I don't want to have the students run Pkg.add(...)/Pkg.update(), > as packages have a tendency to occasionally break on updates, and it's a > headache dealing with this during the lecture. > > Two possible solutions I can think of of are: > > 1) Prebake a .julia folder that contains all the necessary resources, > with a script to reset in case the students break it with Pkg.update(). > 2) Use system image > > http://docs.julialang.org/en/release-0.4/devdocs/sysimg/ > > that includes all the necessary packages. It's not really clear how to > do this from the documentation, though. I'm also not sure how that would > interact with Pkg.update() though, so probably instructions to delete > .julia would also need to be given. > > > Any other options I'm missing? If 2 is recommended, any tutorial how to > do this? >
