/usr/share/doc/wajig/README is in wajig 2.2.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
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 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 | JIG has evolved over several years of using and maintaining Debian
systems. It attempts to capture in a single command line tool (and a
simple companion GNOME GUI) various things I commonly do that relate to
managing the system. Many of the commands supported by wajig have been
gleemed from hints and gossip on the mailing lists, and sometimes
nuggets of useful information from the documentation.
For a brief summary of only the most common commands try "wajig help".
Online documentation is available at
http://www.togaware.com/linux/survivor/wajig.shtml.
If you experience trouble with the display, or see what would appear
to be incomplete output from wajig, consider running the "wajig reset"
command to see if that fixes the problem.
Dirk Eddelbuettel <edd@debian.org> has also been incredibly helpful in
sponsoring wajig for inclusion in Debian and in suggesting new
commands. Also, many thanks to other users of wajig who have made
suggestions over the years.
--> words by Graham Williams & updated/fixed by Tshepang Lekhonkhobe
HACKING
setup:
$ wajig install devscripts
$ hg clone https://wajig.googlecode.com/hg
$ cd wajig
build + install:
$ debuild -us -uc -b
$ sudo debi
guidelines:
* follow PEP-8 where it makes sense ($ pep8 src/wajig.py)
* run pylint on the changed files ($ pylint src/wajig.py)
* add unit tests (to "test.py") if your code is easily testable
* ensure the unit tests pass before any commits
* ensure that new features and changes are documented
(look in "src/documentation.py" and "help/")
* ensure that user-visible changes are mentioned in "debian/changelog"; use
debchange from within the project root directory and do your changes there
|