Comment 5 for bug 1564622

I think that gets to be a bit much. I'd rather keep it simple if we can.

On Mon, Apr 11, 2016, 5:15 PM Nate Finch <email address hidden> wrote:

> We can always run `juju-1 version` to find the local version of the
> binary.
>
> I wonder if we want to give more of an introduction to Juju 2.
> Something along the lines of:
>
> Welcome to Juju 2.0. The 'juju' command now refers to the 2.0 version
> of Juju. If you wish to interact with a Juju 1.x environment, please use
> the existing Juju <1.x.x> command juju-1, as the Juju 2.0 command cannot
> interact with Juju 1.x environments.
>
> Note that many commands have changed in Juju 2.0. Please see
> https://jujucharms.com/SomeValidURL for more information, or type 'juju
> help'.
>
> Would you like to run the 'juju <whatever>' command you entered with
> juju 2.0? Y/n?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1565991).
> https://bugs.launchpad.net/bugs/1564622
>
> Title:
> Suggest juju1 upon first use of juju2 if there is an existing
> JUJU_HOME dir
>
> Status in juju-core:
> Triaged
>
> Bug description:
> Users with existing juju 1.x environments may be surprised when doing
> a dist upgrade if juju2 is the default in update-alternatives and they
> can no longer talk to their 1.x environments.
>
> Juju2 can be updated to look for a JUJU_HOME dir upon first use (when
> creating JUJU_DATA), or when it can't find any information in
> JUJU_DATA to suggest that users can use update-alternatives to use
> juju1 to talk to existing environments.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1564622/+subscriptions
>