Merge lp:~gary/charms/precise/juju-gui/bug1218888 into lp:~juju-gui/charms/precise/juju-gui/trunk
Status: | Merged | ||||
---|---|---|---|---|---|
Merged at revision: | 117 | ||||
Proposed branch: | lp:~gary/charms/precise/juju-gui/bug1218888 | ||||
Merge into: | lp:~juju-gui/charms/precise/juju-gui/trunk | ||||
Diff against target: |
209 lines (+82/-37) 2 files modified
hooks/utils.py (+7/-3) tests/test_utils.py (+75/-34) |
||||
To merge this branch: | bzr merge lp:~gary/charms/precise/juju-gui/bug1218888 | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
charmers | Pending | ||
Review via email: mp+190971@code.launchpad.net |
Description of the change
Add support for xz compression
An xz tarball reduces the size of the gui code by 30 to 40 percent. These changes let the charm use xz tarballs. A very simple change to the gui makefile will follow.
To qa, apply this diff to the gui trunk:
=== modified file 'Makefile'
--- Makefile 2013-10-12 01:30:26 +0000
+++ Makefile 2013-10-14 13:43:10 +0000
@@ -95,7 +95,7 @@
LAUNCHPAD_
endif
RELEASE_
-RELEASE_
+RELEASE_
RELEASE_
NPM_CACHE_
NPM_CACHE_
Then run ``BRANCH_IS_GOOD=1 make distfile``. Copy over the new release to the charm's releases directory. If you compare the two file sizes in the charm's releases directory, the difference should be dramatic.
$ ls -l
-rw-r--r-- 1 gary gary 5076088 Oct 14 09:44 juju-gui-
-rw-r--r-- 1 gary gary 44840221 Oct 12 20:15 juju-gui-0.10.1.tgz
You can remove the tgz, and then run juju bootstrap and make deploy in the charm root directory. Once it is deployed, you should be able to log in and see the gui as usual, and you should be able to verify the fact that you are using your custom release if you go to /juju-ui/
Thank you!
Reviewers: mp+190971_ code.launchpad. net,
Message:
Please take a look.
Description:
Add support for xz compression
An xz tarball reduces the size of the gui code by 30 to 40 percent.
These changes let the charm use xz tarballs. A very simple change to
the gui makefile will follow.
To qa, apply this diff to the gui trunk:
=== modified file 'Makefile' API_ROOT= staging NAME=juju- gui-$(RELEASE_ VERSION) FILE=releases/ $(RELEASE_ NAME).tgz FILE=releases/ $(RELEASE_ NAME).xz SIGNATURE= releases/ $(RELEASE_ NAME).asc VERSION= $(BZR_REVNO) FILE=$( CURDIR) /releases/ npm-cache- $(NPM_CACHE_ VERSION) .tgz
--- Makefile 2013-10-12 01:30:26 +0000
+++ Makefile 2013-10-14 13:43:10 +0000
@@ -95,7 +95,7 @@
LAUNCHPAD_
endif
RELEASE_
-RELEASE_
+RELEASE_
RELEASE_
NPM_CACHE_
NPM_CACHE_
Then run ``BRANCH_IS_GOOD=1 make distfile``. Copy over the new release
to the charm's releases directory. If you compare the two file sizes in
the charm's releases directory, the difference should be dramatic.
$ ls -l 0.10.1+ build.1133. xz
-rw-r--r-- 1 gary gary 5076088 Oct 14 09:44
juju-gui-
-rw-r--r-- 1 gary gary 44840221 Oct 12 20:15 juju-gui-0.10.1.tgz
You can remove the tgz, and then run juju bootstrap and make deploy in version. js, where you will see something like "var nfo=['unrelease d', '1133'];".
the charm root directory. Once it is deployed, you should be able to
log in and see the gui as usual, and you should be able to verify the
fact that you are using your custom release if you go to
/juju-ui/
jujuGuiVersionI
Thank you!
https:/ /code.launchpad .net/~gary/ charms/ precise/ juju-gui/ bug1218888/ +merge/ 190971
(do not edit description out of merge proposal)
Please review this at https:/ /codereview. appspot. com/14425057/
Affected files (+84, -37 lines):
A [revision details]
M hooks/utils.py
M tests/test_utils.py