Yes. In the User Behavior I can change the julia path to use any version, but what's happening is when I put 0.4.3 to juno, it thows so many depreciation warnings and that's kind of annoying.
On Monday, March 7, 2016 at 8:57:53 PM UTC+5:30, Mike Innes wrote: > > You don't have to use Juno with the bundled copy of Julia, you can point > it to the external (0.4.3) version and use the same for both. Just poke > around in the settings and you should find the option. > On Mon, 7 Mar 2016 at 04:44 Vishnu Raj <ee14...@ee.iitm.ac.in > <javascript:>> wrote: > >> In my system I have Juno with 0.4.2 and julia with 0.4.3. Every time I >> start one, all my packages are getting recompiled. They are all under same >> v0.4 folder and I think that's why this is happening. >> Is there a way to avoid this? >> >> >> On Sunday, March 6, 2016 at 3:28:40 PM UTC+5:30, Andreas Lobinger wrote: >>> >>> Depends on your definition of installed and what system you use. I use >>> since 0.2 (and the 0.3dev) a local build -on a linux system- and this quite >>> nicely encapsulated in a single directory inside my home so they live in >>> parallel. The package directory which is inside .julia is has versioning >>> (v0.3/v0.4/v0.5), too. >>> >>> On Saturday, March 5, 2016 at 11:48:37 PM UTC+1, Pulkit Agarwal wrote: >>>> >>>> Hi, >>>> >>>> Is there a way to have the stable version of Julia as the global Julia >>>> (i.e. something which can be accessed by calling `julia` from the command >>>> line) and the development version of Julia (which will be stored in some >>>> other folder). >>>> >>>> Thanks, >>>> Pulkit >>>> >>>
