I usually don't value backwards-compatibility very highly if it's not too much of a hassle to stay up-to-date (and it isn't with Julia), but I still think moving everything into a .julia/vX.Y folder is a terrific idea - there's really no other way to make *non*-backwards-compatible changes and still let several versions coexist on the same system. Break whatever you want when going from 0.2 to 0.3 (or 1.5 to 1.6, when we get there), but keep the installations separate - that way I can always go back to the old version if I liked it better (or if I just need to recover something and port it manually).
// T On Monday, June 9, 2014 4:33:12 PM UTC+2, Kevin Squire wrote: > > Sorry...! > > > On Mon, Jun 9, 2014 at 7:28 AM, Stefan Karpinski <ste...@karpinski.org > <javascript:>> wrote: > >> Sigh. I guess I should really come to terms with the fact that I will >> have to worry about versioning and compatibility from now on... >> >> >> On Mon, Jun 9, 2014 at 10:20 AM, Kevin Squire <kevin....@gmail.com >> <javascript:>> wrote: >> >>> Especially for those upgrading from v0.2, it might be nice to provide a >>> smooth transition. And there is also the issue mentioned by Matt, where >>> some users may want to use both v0.2 and v0.3 on the same system. >>> >>> I vote for moving the history to the version subdirectory (if it exists). >>> >>> Cheers, >>> Kevin >>> >>> >>> On Mon, Jun 9, 2014 at 7:16 AM, Milan Bouchet-Valat <nali...@club.fr >>> <javascript:>> wrote: >>> >>>> Le lundi 09 juin 2014 à 09:43 -0400, Stefan Karpinski a écrit : >>>> > "Automatic" and "delete" aren't things I like in the same sentence. >>>> In general, sure, but we're talking about command history, not the >>>> user's photo library... ;-) >>>> >>>> >>> >> >
