3
| |::\ / /::\ / /:/ / /::\
4
| |:|:\ / /:/\:\ /__/::\ / /:/\:\
5
__|__|:|\:\ / /:/ \:\ \__\/\:\ / /:/ \:\
6
/__/::::| \:\ /__/:/ \__\:\ \ \:\ /__/:/ \__\:\
7
\ \:\~~\__\/ \ \:\ / /:/ \__\:\ \ \:\ / /:/
8
\ \:\ \ \:\ /:/ / /:/ \ \:\ /:/
9
\ \:\ \ \:\/:/ /__/:/ \ \:\/:/
10
\ \:\ \ \::/ \__\/ \ \::/
13
4
If you're trying to hack on Mojo, you can run "sudo python setup.py install"
14
5
against a branch of Mojo to install it. You'll need codetree installed as well,
15
6
which you can install in a similar way once grabbing lp:codetree.
17
See the README's FAQ for further tips/gotchas.
8
See the [README](readme.html)'s FAQ for further tips/gotchas.
19
10
To build an updated version of the mojo package:
21
1. Ensure the name of the directory you're using is "mojo" (debian
12
1. Ensure the name of the directory you're using is "mojo" (debian
22
13
packaging will look for this).
23
2. Increment the version in ./setup.py
24
3. `make deb`. If you need to rerun for some reason (missing dependencies,
14
2. Increment the version in ./setup.py
15
3. `make deb`. If you need to rerun for some reason (missing dependencies,
25
16
etc.), just re-run `debuild -sa -I.bzr` from the debian directory, as `make
26
17
deb` will update the changelog again.
27
4. Upload the .changes file from a directory level above the Makefile
18
4. Upload the .changes file from a directory level above the Makefile