Merge lp:~mbruzek/juju-release-tools/packaging-juju2-default into lp:~juju-qa/juju-release-tools/packaging-juju2-default

[Matt Bruzek]

This is the change that was discussed with Martin and Nicholas. To symbolically link juju to the juju-2.0 file. Please evaluate this as a solution to https://bugs.launchpad.net/juju-core/+bug/1600257

However there were alternate solutions discussed, to work with juju1 packaging, such as renaming the source file juju-2.0 to juju if I remember correctly.

If this solution is determined to be less than optimal, go ahead and close it. I wanted to present my proposal against the right branch so we could evaluate the pros and cons of this approach.

[Nicholas Skaggs (nskaggs)]

Ugh, sorry Matt. So much going on with the release, I had forgotten about this.

[Nicholas Skaggs (nskaggs)]

Thanks again!

review: Approve

=== modified file 'debian/rules'
--- debian/rules	2016-06-30 22:04:52 +0000
+++ debian/rules	2016-07-09 14:33:11 +0000
@@ -56,6 +56,7 @@
 	dh_auto_install
 
 override_dh_link:
+	dh_link -pjuju-2.0 usr/share/bash-completion/completions/juju-2.0 usr/share/bash-completion/completions/juju
 	dh_link -pjuju-2.0 usr/lib/juju-$(VERSION)/bin/juju usr/bin/juju
 	dh_link -pjuju-2.0 usr/lib/juju-$(VERSION)/bin/jujud usr/bin/jujud
 	dh_link -pjuju-2.0 usr/lib/juju-$(VERSION)/bin/juju-metadata usr/bin/juju-metadata