<articleinfo>
<title>Configuration management</title>
- <subtitle>Protocol version 2</subtitle>
- <releaseinfo>Revision 7.0</releaseinfo>
+ <subtitle>Protocol version 2.1</subtitle>
+ <releaseinfo>Revision 7.1</releaseinfo>
<author>
<firstname>
Wichert
So, what do we need to store in a variable template? Of course we
need a name to identify the template. Template names are made up of
components separated by the character `/' (slash).
- Each component is limited to alphanumerics and `+' `-' `.'
- (plus, minus, full stop).
+ Each component is limited to alphanumerics and `+' `-' `.' `_'
+ (plus, minus, full stop, underscore).
</para>
<para>
A type is also needed so data can be verified. Here is a table
For localization, the description field (and also the choices
field of a select or multiselect type question, and the
default field of a string or password type question) can be
- supplimented with versions for other languages. These are
+ supplemented with versions for other languages. These are
named <emphasis>Description-ll</emphasis>,
<emphasis>Description-ll_LL</emphasis>,
<emphasis>Description-ll_LL.encoding</emphasis> and so on.
usually run <emphasis>before</emphasis> the preinst, and before
the package is unpacked!
<note>
- <simpara>Plese see debconf-devel(8) for details.</simpara>
+ <simpara>Please see debconf-devel(7) for details.</simpara>
</note>
This is done to make sure that we can
use the desired configuration in the preinst if necessary.