Since I use both master and 1.0, I was wondering if I could somehow maintain a consistent environment of packages (ie the global Project.toml and Manifest.toml in ~/.julia/environments/VERSION) between the two, to make it easier to switch back and forth.
Just checking, could this have any unintended downsides I am not seeing?
Regarding the implementation, can I just symlink ~/.julia/environments/v1.1 etc to ~/.julia/environments/v1.1, or is there a more canonical way of doing this?
Though option when deving is to just activate the package dir, or your working environment (if dev --local) in each by name/command line arg.
Which is l what I almost do, since I never use default environment at all.
First thing I’d try is moving ~/.julia/environments/v1.1 somewhere temporary and replacing it with a symlink to ~/.julia/environments/v1.0. Probably want to make a back up of that directory first, though, since some of its contents will be modified.
Though a safer (but harder) option might be to create a script that scans the manifests and syncs them.
Maybe another alternative; I have a separate depot/environments/common and use JULIA_LOAD_PATH="@common::". Could use ::@common if you want the v1.1 prompt, but then installing stuff into the common environment is annoying (unless there’s a way to switch?)