[Openvas-commits] r4060 - trunk/doc/website

[scm-commit@wald.intevation.org]

Author: mattm
Date: 2009-07-16 11:39:38 +0200 (Thu, 16 Jul 2009)
New Revision: 4060

Modified:
   trunk/doc/website/openvas-cr-38.htm4
Log:
Adjust actions on libomp and libotp.

Modified: trunk/doc/website/openvas-cr-38.htm4
===================================================================
--- trunk/doc/website/openvas-cr-38.htm4	2009-07-16 08:28:32 UTC (rev 4059)
+++ trunk/doc/website/openvas-cr-38.htm4	2009-07-16 09:39:38 UTC (rev 4060)
@@ -48,7 +48,7 @@
 
 <p>
 This change was discussed in a session at the OpenVAS DevCon-2
-in Juli 2009.
+in July 2009.
 </p>
 
 <h3>Rationale</h3>
@@ -66,6 +66,7 @@
 <li> openvas-manager:libotp (static)
 <li> openvas-manager:libmanage (static)
 <li> openvas-manager:libstring (static)
+<li> openvas-manager:libfile (static)
 <li> openvas-manager:libovas-mngr-comm (static)
 <li> openvas-manager:libcommon (static)
 </ul>
@@ -87,7 +88,7 @@
 in terms of copyright and license), a consolidation
 will less trouble new developers. Clean rules on
 where to place API elements will provide a guide
-to more easily involve into the developments. 
+to more easily involve into the developments.
 </p>
 
 <p>
@@ -126,7 +127,7 @@
 </p>
 
 <ul>
-<li> openvas-libraries/nasl: The the nasl library (contents of
+<li> openvas-libraries/nasl: The nasl library (contents of
      openvas-libnasl/nasl)
 <li> openvas-libraries/base: openvas-libraries/libopenvascommon/ and all
      other basic API methods that are of general use but do not involve
@@ -138,16 +139,17 @@
      until consolidated into other library or resolved in another way.
 <li> openvas-libraries/net: Low-level networking functions that require
      dependencies to low level system libraries.
-<li> openvas-libraries/omp: API for OMP clients (libomp and libcommon from
-     openvas-manager as a start. Need to be extended with full API).
-<li> openvas-libraries/otp: API for OTP clients (libotp from openvas-manager
-     as a early start, needs to be extended with full API later on).
+<li> openvas-libraries/omp: API for OMP clients (libcommon from
+     openvas-manager as a start.  Needs to be extended with full API).
+<li> openvas-libraries/otp: API for OTP clients.  Empty initially, with the
+     idea of extending to a full API in the future.
 </ul>
 
 <p>
-The other libraries of openvas-manager (libmanage, libopenvas-mngr-comm
-and libstring) remain with that module as long as they are not
-required by any other module.
+The other libraries of openvas-manager (libomp, libotp, libmanage,
+libopenvas-mngr-comm and libstring) remain with that module as long as they
+are not required by any other module.  libomp and libotp need to be renamed
+as they clash with openvas-libraries.
 </p>
 
 <p>
@@ -156,7 +158,7 @@
 </p>
 
 <p>
-It is still to decide wether to move towards cmake and disregard
+It is still to decide whether to move towards cmake and disregard
 the current autotools approach for configuration of source code
 package. As autotools and cmake do not necessarily conflict
 when used in the same module, the new libraries will be managed
@@ -167,6 +169,8 @@
 <h3>History</h3>
 
 <ul>
+<li> 2009-07-16 Matthew Mundell &lt;mmundell at intevation.de&gt;:<br>
+     Adjust actions on libomp and libotp.</li>
 <li> 2009-07-14 Jan-Oliver Wagner &lt;jan-oliver.wagner at intevation.de&gt;:<br>
      Initial text. This is a result of a session at OpenVAS DevCon2.</li>
 </ul>