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