OpenPKG CVS Repository
http://www.openpkg.org/cvsweb/cvsweb.cgi
____________________________________________________________________________
Server: cvs.openpkg.org Name: Michael Schloh
Root: /e/openpkg/cvs Email: [EMAIL PROTECTED]
Module: openpkg-doc Date: 13-Aug-2002 13:46:33
Branch: HEAD Handle: 2002081312463300
Modified files:
openpkg-doc/handbook openpkg.xml
Log:
Added more detailed explanation of configuration options and their relation to
release testing.
Summary:
Revision Changes Path
1.55 +34 -9 openpkg-doc/handbook/openpkg.xml
____________________________________________________________________________
Index: openpkg-doc/handbook/openpkg.xml
============================================================
$ cvs diff -u -r1.54 -r1.55 openpkg.xml
--- openpkg-doc/handbook/openpkg.xml 5 Aug 2002 15:53:02 -0000 1.54
+++ openpkg-doc/handbook/openpkg.xml 13 Aug 2002 11:46:33 -0000 1.55
@@ -1494,15 +1494,40 @@
This method of semi-customization works when building with
'--rebuild' and '-bb' as well. Because the use of such custom
definitions are not just limited to the build process, it is
- possible that the '--define' option will be used during installation
- as well. When in doubt, customize a package in this way by giving
- the same '--define' option at each step of the build and install
- process. For more information on how to use the custom configuration
- features of OpenPKG, a quick study of an RPM .spec file can yield
- much. Of course, choose a package which has such internal
- configuration variables. Search a .spec file for 'with_' to find out
- if the package offers such customization. This is also useful in
- learning which configuration options a package allows.
+ possible that the '--define' option variables will be used during
+ installation as well. When in doubt, customize a package in this way
+ by giving the same '--define' option at each step of the build and
+ install process. For more information on how to use the custom
+ configuration features of OpenPKG, a quick study of an RPM .spec
+ file can yield much. Of course, choose a package which has such
+ internal configuration variables. Search a .spec file for 'with_' to
+ find out if the package offers such customization. This is also
+ useful in learning which configuration options a package allows.
+ </para>
+ <para>
+ Starting with the OpenPKG 1.1 release, all semi-custom option
+ variables are listed in the description section of a spec file. To
+ learn which configuration options a package offers, use the same
+ RPM command as to view its description text. When installing
+ packages without explicitly stating the available configuration
+ options, defaults will be used. When the configuration option
+ concerns extra functionality, a typical default value is to not
+ install the extra functionality and opt for a standard installation
+ instead.
+ </para>
+ <para>
+ Along the same lines, OpenPKG packages with optional features are
+ tested only through common usage and not through a rigorous and
+ exhaustive combinational test. Although part of the release
+ process guarantees that packages will be buildtime tested, no
+ guarantee is implied in the building of semi-custom packages
+ configured with options. Doing so would require an exponentially
+ greater amount of testing (and thus exponentially longer delay in
+ release cycle). Imagine testing each combination of just the
+ 'apache' package with around forty options. It would cost a tester
+ 1.1e+12 (2 ^ 40) times the amount of time and resources to conclude
+ exhaustive testing should the tester take all options and their
+ combinations into consideration!
</para>
</sect2>
______________________________________________________________________
The OpenPKG Project www.openpkg.org
CVS Repository Commit List [EMAIL PROTECTED]
