blob: 5bd1c180a16003d3b18786ce8fecc9039f488486 [file] [log] [blame]
martin f. krafft46c06522013-07-03 20:03:22 +02001=============================================================
2 reclass recursive external node classification
3=============================================================
4reclass is © 20072013 martin f. krafft <madduck@madduck.net>
5and available under the terms of the Artistic Licence 2.0
6'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
7
8Installation
9~~~~~~~~~~~~
10If you just want to run reclass from source, e.g. because you are going to be
11making and testing changes, install it in "development mode":
12
13 python setup.py develop
14
martin f. krafft30943272013-07-04 08:32:00 +020015Now the reclass script, as well as the adapters, will be available in
16/usr/local/bin, and you can also invoke them directly from the source tree.
17
martin f. krafft46c06522013-07-03 20:03:22 +020018To uninstall:
19
20 python setup.py develop --uninstall
21
22Discussing reclass
23~~~~~~~~~~~~~~~~~~
24If you want to talk about reclass, the best way right now is to use the
25salt-users mailing list (please put 'reclass' into the subject), or to find me
26on IRC, either 'madduck' in the #salt/freenode channel, or in #reclass/oftc.
27
28Contributing to reclass
29~~~~~~~~~~~~~~~~~~~~~~~
30Conttributions to reclass are very welcome. Since I prefer to keep a somewhat
31clean history, I will not just merge pull request.
32
33You can submit pull requests, of course, and I'll rebase them onto HEAD before
34merging. Or send your patches using git-format-patch and git-send-e-mail to
35reclass@pobox.madduck.net.
36
37I have added rudimentary unit tests, and it would be nice if you could submit
38your changes with appropriate changes to the tests. To run tests, invoke
martin f. kraffta5c998e2013-07-05 08:50:10 +020039
martin f. krafft96a6aff2013-08-07 16:32:56 +020040 $ make tests
martin f. kraffta5c998e2013-07-05 08:50:10 +020041
martin f. krafft96a6aff2013-08-07 16:32:56 +020042in the top-level checkout directory. The tests are rather inconsistent, some
43using mock objects, and only the datatypes-related code is covered. If you are
44a testing expert, I could certainly use some help here to improve the
45consistency of the existing tests, as well as their coverage.
martin f. kraffta5c998e2013-07-05 08:50:10 +020046
47Also, there is a Makefile giving access to PyLint and coverage.py (running
48tests). If you run that, you can see there is a lot of work to be done
49cleaning up the code. If this is the sort of stuff you want to do by all
50means be my guest! ;)
martin f. krafft46c06522013-07-03 20:03:22 +020051
52If you have larger ideas, I'll be looking forward to discuss them with you.
53
martin f. krafft96a6aff2013-08-07 16:32:56 +020054 -- martin f. krafft <madduck@madduck.net> Wed, 07 Aug 2013 16:21:04 +0200