On 06/04/2016, Stuart Bishop <stuart.bis...@canonical.com> wrote: > > How do our plugins know what version of juju is in play? Can they > assume that the 'juju' binary found on the path is the juju that > invoked the plugin, or is there some other way to tell using > environment variables or such? Or will all the juju plugins just fail > if they are invoked from the non-default juju version?
The new packaging uses wrapping scripts for 'juju-1' and 'juju-2.0' that prepend PATH with the version-specific directories. The default /usr/bin/juju is just a symlink though, so invoking outside the context of the wrappers will still be ambiguous. I think we do need a better solution here. Martin -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
