I do this as well to test changes quickly on 0.3.10. You might consider calling Pkg.pin() so it's less likely to flip-flop when calling update, but that could bring its own problems I suppose. I primarily use 0.4 so I haven't had any issues.
On Friday, July 24, 2015, Elliot Saba <[email protected]> wrote: > The time when this could go awry is if you were to update your package to > support only 0.3 or only 0.4, then the versions of the package that each > version of Julia would attempt to load would be different, resulting in the > directory flip-flopping between the 0.3 and 0.4 versions every time you > pkg.update(). > -E > > On Fri, Jul 24, 2015 at 4:25 PM, andrew cooke <[email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote: > >> seems to work fine. >> >> >> On Friday, 24 July 2015 18:36:05 UTC-3, andrew cooke wrote: >>> >>> If I am developing a package with multiple julia versions, will anything >>> terrible happen if I Pkg.clone() the project twice (one for each version) >>> and then replace one of those directories with a link to the other? >>> >>> So change from >>> >>> .julia/v0.3/MyPackage >>> .julia/v0.4/MyPackage >>> >>> to >>> >>> .julia/v0.3/MyPackage >>> .julia/v0.4/[link to above] >>> >>> and then use git commands directly? >>> >>> Could I run Pkg.test() for either version? >>> >>> Is anything likely to go wrong? >>> >>> Thanks. >>> Andrew >>> >> >
