diff options
author | Holger Weiss <holger@zedat.fu-berlin.de> | 2009-05-19 12:18:02 (GMT) |
---|---|---|
committer | Holger Weiss <holger@zedat.fu-berlin.de> | 2009-05-19 12:18:02 (GMT) |
commit | b6362e9cf5a7cdf4489e44c9e84cc2d085d89dc2 (patch) | |
tree | abd9deb8396ec3faea8e15783bb7f95e70b1c68a /doc/developer-guidelines.sgml | |
parent | cfbc87b2d36a8128a0b938b6758ed79399423ae1 (diff) | |
download | monitoring-plugins-b6362e9cf5a7cdf4489e44c9e84cc2d085d89dc2.tar.gz |
Talk about Git instead of CVS
Update the Developer Guidelines to reflect the fact that our development
is done using Git instead of CVS these days (as noted by Chris Pepper on
the "nagiosplug-devel" list).
While at it, apply another few minor cleanups.
Signed-off-by: Holger Weiss <holger@zedat.fu-berlin.de>
Diffstat (limited to 'doc/developer-guidelines.sgml')
-rw-r--r-- | doc/developer-guidelines.sgml | 26 |
1 files changed, 13 insertions, 13 deletions
diff --git a/doc/developer-guidelines.sgml b/doc/developer-guidelines.sgml index 132fada..583f725 100644 --- a/doc/developer-guidelines.sgml +++ b/doc/developer-guidelines.sgml | |||
@@ -11,7 +11,7 @@ | |||
11 | </author> | 11 | </author> |
12 | </authorgroup> | 12 | </authorgroup> |
13 | 13 | ||
14 | <pubdate>2006</pubdate> | 14 | <pubdate>2009</pubdate> |
15 | <title>Nagios plug-in development guidelines</title> | 15 | <title>Nagios plug-in development guidelines</title> |
16 | 16 | ||
17 | <revhistory> | 17 | <revhistory> |
@@ -22,7 +22,7 @@ | |||
22 | </revhistory> | 22 | </revhistory> |
23 | 23 | ||
24 | <copyright> | 24 | <copyright> |
25 | <year>2000 - 2006</year> | 25 | <year>2000 - 2009</year> |
26 | <holder>Nagios Plugins Development Team</holder> | 26 | <holder>Nagios Plugins Development Team</holder> |
27 | </copyright> | 27 | </copyright> |
28 | 28 | ||
@@ -34,7 +34,7 @@ | |||
34 | the plug-in developers and encourage the standarization of the | 34 | the plug-in developers and encourage the standarization of the |
35 | different kind of plug-ins: C, shell, perl, python, etc.</para> | 35 | different kind of plug-ins: C, shell, perl, python, etc.</para> |
36 | 36 | ||
37 | <para>Nagios Plug-in Development Guidelines Copyright (C) 2000-2006 | 37 | <para>Nagios Plug-in Development Guidelines Copyright (C) 2000-2009 |
38 | (Nagios Plugins Team)</para> | 38 | (Nagios Plugins Team)</para> |
39 | 39 | ||
40 | <para>Permission is granted to make and distribute verbatim | 40 | <para>Permission is granted to make and distribute verbatim |
@@ -50,18 +50,18 @@ | |||
50 | <para> | 50 | <para> |
51 | Nagios plugins are developed to the GNU standard, so any OS which is supported by GNU | 51 | Nagios plugins are developed to the GNU standard, so any OS which is supported by GNU |
52 | should run the plugins. While the requirements for compiling the Nagios plugins release | 52 | should run the plugins. While the requirements for compiling the Nagios plugins release |
53 | is very small, to develop from CVS needs additional software to be installed. These are the | 53 | are very basic, developing from the Git repository requires additional software to be |
54 | minimum levels of software required: | 54 | installed. These are the minimum levels of software required: |
55 | 55 | ||
56 | <literallayout> | 56 | <literallayout> |
57 | gnu make 3.79 | 57 | GNU make 3.79 |
58 | automake 1.9.2 | 58 | GNU automake 1.9.2 |
59 | autoconf 2.59 | 59 | GNU autoconf 2.59 |
60 | gnu m4 1.4.2 | 60 | GNU m4 1.4.2 |
61 | gnu libtool 1.5 | 61 | GNU libtool 1.5 |
62 | </literallayout> | 62 | </literallayout> |
63 | 63 | ||
64 | To compile from CVS, after you have checked out the code, run: | 64 | To compile from Git, after you have cloned the repository, run: |
65 | <literallayout> | 65 | <literallayout> |
66 | tools/setup | 66 | tools/setup |
67 | ./configure | 67 | ./configure |
@@ -748,7 +748,7 @@ setup the tests. Run "make test" to run all the tests. | |||
748 | update the THANKS.in file.</para> | 748 | update the THANKS.in file.</para> |
749 | <para>If you have a change that is useful for noting in the next release, please | 749 | <para>If you have a change that is useful for noting in the next release, please |
750 | update the NEWS file.</para> | 750 | update the NEWS file.</para> |
751 | <para>All CVS commit comments will be written to a ChangeLog at release time. | 751 | <para>All commit comments will be written to a ChangeLog at release time. |
752 | </para> | 752 | </para> |
753 | </section> | 753 | </section> |
754 | 754 | ||
@@ -784,7 +784,7 @@ update the THANKS.in file.</para> | |||
784 | <section id="Patches"><title>Patches</title> | 784 | <section id="Patches"><title>Patches</title> |
785 | <para>If you have a bug patch, please supply a unified or context diff against the | 785 | <para>If you have a bug patch, please supply a unified or context diff against the |
786 | version you are using. For new features, please supply a diff against | 786 | version you are using. For new features, please supply a diff against |
787 | the CVS HEAD version.</para> | 787 | the Git "master" branch.</para> |
788 | 788 | ||
789 | <para>Patches should be submitted via | 789 | <para>Patches should be submitted via |
790 | <ulink url="http://sourceforge.net/tracker/?group_id=29880&atid=397599">SourceForge's | 790 | <ulink url="http://sourceforge.net/tracker/?group_id=29880&atid=397599">SourceForge's |