Ideally we don't have that many aliases for the same thing (and some of those /usr/bin files are not from our latest packaging)?
I think what you really want is to just run `/usr/bin/juju` but realise having juju-1-default makes that more complicated as well. So, I see some benefit in a any-2-series juju alias, but think we'll get pushback on usability of having too many similarly named commands installed by default. See thread from when this was originally being discussed for some more info: <https://lists.ubuntu.com/archives/juju-dev/2016-April/005313.html> ** Changed in: juju-core Importance: Undecided => High ** Changed in: juju-core Status: New => Triaged ** Changed in: juju-core Milestone: None => 2.1.0 ** Also affects: juju-core (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613864 Title: Missing "juju-2"/"juju2" command. To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1613864/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
