I was on 0.4 but daily updates from git just broke too often… I always did make clean as a norm because it saved time in the end…
Having said that, since my GCC is 4.9.x, and I understand GCC has moved to 5.x.x I might just change GCC and thus reinstall from 0… Cheers F > On 10 Aug 2015, at 23:10, Tony Kelman <t...@kelman.net> wrote: > > You would likely need at least `make clean`, probably `make cleanall` as well > when switching between release-0.3 and the forthcoming release-0.4 branch. > Many of the dependency versions have changed, though not all. It will likely > be more reliable to at least rebuild the dependencies that have changed > versions, which `make cleanall` should usually do for you - it deletes the > installed copies from ./usr which forces the right version to be > re-installed, though it won't completely delete the built copies of the > dependencies from ./deps. > > > On Monday, August 10, 2015 at 10:14:31 AM UTC-7, Scott T wrote: > Within the next month unless something unexpected happens, I'd say - you can > follow discussion on the last few milestones here. > > Cheers, > Scott > > On Monday, 10 August 2015 17:14:41 UTC+1, Federico Calboli wrote: > Thanks! So something like > > git pull && git checkout release-0.4 && make > > should work... Any idea of when 0.4 will be out as stable (I know it is out > as development)? > > Cheers > > F > > On Monday, 10 August 2015 16:50:12 UTC+3, Scott T wrote: > In fact, I imagine there will be a release-0.4 branch instead of a tag, so > you will probably be able to ignore the "git fetch --tags" and do something > more like "git checkout release-0.4". Anyway, my point being that quite a lot > will change in v0.4 so it's best to run the upgrade yourself (and you can do > it without deleting everything and starting again). There will definitely be > instructions available! > > Scott > > On Monday, 10 August 2015 14:44:07 UTC+1, Scott T wrote: > Hi Federico, > > I think that what you need is as simple as doing something like > > git fetch --tags > git pull > git checkout v0.4.0 > make > > from within the git repo once version 0.4.0 is out. It's not quite "magical", > but you will probably want to push the button on the upgrade yourself instead > of having it take you by surprise. > > Cheers, > Scott > > On Monday, 10 August 2015 12:07:51 UTC+1, Federico Calboli wrote: > Hi All, > > (assuming this is the right forum), according to the instructions here: > > https://github.com/JuliaLang/julia > > I can run the 'stable' release by cloning the git repo and then checking out > the 0.3 release. Now, I presume the 0.4 release will eventually become > 'stable', and so on and so forth. My lack of git-foo menas that I would then > remove the whole /usr/local/julia directory and start from scratch with the > new stable release. This is doable but I was wondering whether there is a > way of tracking the stable release that will magically upgrade the whole > thing to the next stable release when it is available. > > Cheers > > F -- Federico Calboli f.calb...@gmail.com
