I kept a separate directory for a checkout of the release-0.2 branch in order to be able to test things with old Julia. If you switch branches regularly, you will spend much time recompiling dependencies when they change and you are likely to hit trouble if we fail to future proof the make rules.
Ivar kl. 11:31:13 UTC+2 fredag 15. august 2014 skrev Tobias Knopp følgende: > > Yes, but once the release has been made one could also use the tagged > version or use the binaries. > > Am Freitag, 15. August 2014 11:22:27 UTC+2 schrieb Carlos Becker: >> >> To keep up-to-date with the latest changes for v0.3, would it suffice to >> checkout branch release-0.3 periodically? >> Is that the one supposed to have the latest development code for v0.3? >> >> Thanks. >> >> El viernes, 15 de agosto de 2014 07:25:28 UTC+2, Elliot Saba escribió: >>> >>> Your packages should remain untouched through upgrades on minor >>> versions. (E.g. if you were on a 0.3.0 prerelease version before, upgrading >>> to 0.3.0-rc4 or even 0.3.0-final should not affect your packages) >>> >>> If you are on 0.2.1, your packages will probably need to be reinstalled, >>> as Julia separates major versions in the package manager. So you'll just >>> need to Pkg.add() all the packages you had before. This won't erase your >>> 0.2.1 packages, they will persist as long as your `~/.julia/v0.2` directory >>> persists. >>> -E >>> >>> >>> On Fri, Aug 15, 2014 at 1:06 AM, KK Sasa <[email protected]> wrote: >>> >>>> A very basic question: How to update without losing packages? Just >>>> re-install? >>>> >>>> >>>> >>>
