Growing jujud.tgz sizes

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2013-08-12 1:31, David Cheney wrote:
> It is possible 1.12.0 was the only set of tools produced where
> they were not stripped. Stripping go binaries is not recommended,
> but I think it still happens via the ppa:juju/devel build recipe.
> 
> The difference here is the 1.12.0 tools are taken from the saucy 
> package, or their backported versions. These have had dh_strip 
> disabled, which was need to make armhf work.
> 
> So yeah, we have two problems. Probably need to move to .xz, and
> also shouldn't be stripping the tools that go into/come from 
> ppa:juju/devel.


I did test, and after a "juju bootstrap" machine-0 does have a xz
executable available.

The current environs/cloudinit/cloudinit.go adds:

 wget --no-verbose -O - $URL | tar xz -C $bin

Supposedly newer versions of tar support autodetecting what the
compressed stream contains, but I don't know that they support doing
so on stdin.

I have confirmed that:

 cat juju*.tar.xz | tar x

Fails (saying you have to use the -J option), but

 tar x juju*.tar.xz

Does work.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlIIgoEACgkQJdeBCYSNAAM4JQCgtSlBiqT9p1XbEiHqzwzMPcOL
P/gAoLa29eAQcYcZen49vboryeimvWC6
=HEy1
-----END PGP SIGNATURE-----