scripts: add build-release-tarball script

scripts: add build-release-tarball script

First cut of a script which will generate a tarball suitable for packaging.

TODO
* for each dependency, tag and use that tag in the script
* include debian/ packaging in the tarball.

https://code.launchpad.net/~dave-cheney/juju-core/124-scripts-package-release/+merge/171961

(do not edit description out of merge proposal)

[dave_cheney.net, 2013-06-28 06:32:29]

Please take a look.

[gz, 2013-06-28 08:33:04]

LGTM, nice improvement on my throwaway version and will be easy to extend to
read versions from a dep file. Have suggestion about using different VCS
commands, otherwise looks good.

https://codereview.appspot.com/10676046/diff/1/scripts/build-release-tarball/...
File scripts/build-release-tarball/build-release-tarball.bash (right):

https://codereview.appspot.com/10676046/diff/1/scripts/build-release-tarball/...
scripts/build-release-tarball/build-release-tarball.bash:13: bzr branch -r $2 $1
$WORK/src/$3
I'd be tempted to use the bzr-upload plugin command `bzr upload` which generates
a stamp and doesn't include the branch itself.

https://codereview.appspot.com/10676046/diff/1/scripts/build-release-tarball/...
scripts/build-release-tarball/build-release-tarball.bash:19: hg clone -q -r $2
$1 $WORK/src/$3
Would use `hg archive` here rather than clone.

https://codereview.appspot.com/10676046/diff/1/scripts/build-release-tarball/...
scripts/build-release-tarball/build-release-tarball.bash:25: git clone -q $1
$WORK/src/$2
Would use `git archive` rather than clone.

https://codereview.appspot.com/10676046/diff/1/scripts/build-release-tarball/...
scripts/build-release-tarball/build-release-tarball.bash:45: bzr-checkout
lp:juju-core $TAG launchpad.net/juju-core
Should this be tag:$TAG or do we want to leave bzr being smart and checking all
the various revisionspec options?

[dave_cheney.net, 2013-06-28 13:00:56]

Please take a look.

https://codereview.appspot.com/10676046/diff/1/scripts/build-release-tarball/...
File scripts/build-release-tarball/build-release-tarball.bash (right):

https://codereview.appspot.com/10676046/diff/1/scripts/build-release-tarball/...
scripts/build-release-tarball/build-release-tarball.bash:13: bzr branch -r $2 $1
$WORK/src/$3
On 2013/06/28 08:33:04, gz wrote:
> I'd be tempted to use the bzr-upload plugin command `bzr upload` which
generates
> a stamp and doesn't include the branch itself.

Not done, can't be assed with plugins, you already need 24mb of libcurl3-dev
deps.

https://codereview.appspot.com/10676046/diff/1/scripts/build-release-tarball/...
scripts/build-release-tarball/build-release-tarball.bash:19: hg clone -q -r $2
$1 $WORK/src/$3
On 2013/06/28 08:33:04, gz wrote:
> Would use `hg archive` here rather than clone.

Done.

https://codereview.appspot.com/10676046/diff/1/scripts/build-release-tarball/...
scripts/build-release-tarball/build-release-tarball.bash:25: git clone -q $1
$WORK/src/$2
On 2013/06/28 08:33:04, gz wrote:
> Would use `git archive` rather than clone.

Done.

https://codereview.appspot.com/10676046/diff/1/scripts/build-release-tarball/...
scripts/build-release-tarball/build-release-tarball.bash:45: bzr-checkout
lp:juju-core $TAG launchpad.net/juju-core
On 2013/06/28 08:33:04, gz wrote:
> Should this be tag:$TAG or do we want to leave bzr being smart and checking
all
> the various revisionspec options?

I tried add a release-1.11.1 tag this morning, but it completely failed. Once
tags work we can tweak this, but I need to keep the option open for testing of
bodging with -1.

[fwereade, 2013-06-28 14:45:26]

LGTM