Updated translation from Konstantinos Margaritis.

[apt.git] / doc / apt-ftparchive.1.sgml

diff --git a/doc/apt-ftparchive.1.sgml b/doc/apt-ftparchive.1.sgml
index 8107a846f6c4fc57d29ea5d0b996ab2574e5d303..220c4a96c06f2494f89674a3ce6f4e4d6666b805 100644 (file)
--- a/doc/apt-ftparchive.1.sgml
+++ b/doc/apt-ftparchive.1.sgml
@@ -35,6 +35,7 @@
          <arg>packages<arg choice="plain" rep="repeat"><replaceable>path</replaceable></arg><arg><replaceable>override</replaceable><arg><replaceable>pathprefix</replaceable></arg></arg></arg>
          <arg>sources<arg choice="plain" rep="repeat"><replaceable>path</replaceable></arg><arg><replaceable>override</replaceable><arg><replaceable>pathprefix</replaceable></arg></arg></arg>
          <arg>contents <arg choice="plain"><replaceable>path</replaceable></arg></arg>
+         <arg>release <arg choice="plain"><replaceable>path</replaceable></arg></arg>
          <arg>generate <arg choice="plain"><replaceable>config-file</replaceable></arg> <arg choice="plain" rep="repeat"><replaceable>section</replaceable></arg></arg>
          <arg>clean <arg choice="plain"><replaceable>config-file</replaceable></arg></arg>
       </group>
@@ -99,6 +100,25 @@
      The option <option/--db/ can be used to specify a binary caching DB.
      </VarListEntry>
 
+     <VarListEntry><term>release</term>
+     <ListItem><Para>
+     The <literal/release/ command generates a Release file from a
+     directory tree. It recursively searches the given directory for
+     Packages, Packages.gz, Packages.bz2, Sources, Sources.gz,
+     Sources.bz2, Release and md5sum.txt files.  It then writes to
+     stdout a Release file containing an MD5 digest and SHA1 digest
+     for each file.
+     <para>
+     Values for the additional metadata fields in the Release file are
+     taken from the corresponding variables under
+     <literal/APT::FTPArchive::Release/,
+     e.g. <literal/APT::FTPArchive::Release::Origin/.  The supported fields
+     are: <literal/Origin/, <literal/Label/, <literal/Suite/,
+     <literal/Version/, <literal/Codename/, <literal/Date/,
+     <literal/Architectures/, <literal/Components/, <literal/Description/.
+
+     </VarListEntry>
+
      <VarListEntry><term>generate</term>
      <ListItem><Para>
      The <literal/generate/ command is designed to be runnable from a cron script and
@@ -127,7 +147,7 @@
    tree manner. This only effects how the scope tag is handled.
 
    <para>
-   The generate configuration has 4 separate sections, each decribed below.
+   The generate configuration has 4 separate sections, each described below.
 
    <refsect2><title>Dir Section</>
      <Para>
@@ -235,7 +255,7 @@
       to be checked without changing. If this limit is passed the mtime of the 
       contents file is updated. This case can occur if the package file is 
       changed in such a way that does not result in a new contents file 
-      [overried edit for instance]. A hold off is allowed in hopes that new 
+      [override edit for instance]. A hold off is allowed in hopes that new 
       .debs will be installed, requiring a new file anyhow. The default is 10, 
       the units are in days.
       </VarListEntry>
@@ -342,7 +362,7 @@ for i in Sections do
       <VarListEntry><term>Architectures</term>
       <ListItem><Para>
       This is a space separated list of all the 
-      architectures that appear under seach section. The special architecture 
+      architectures that appear under search section. The special architecture 
       'source' is used to indicate that this tree has a source archive.
       </VarListEntry>
       
@@ -459,7 +479,7 @@ for i in Sections do
 
  <RefSect1><title>The Extra Override File</>
    <para>
-   The extra override file allows any arbitary tag to be added or replaced
+   The extra override file allows any arbitrary tag to be added or replaced
    in the output. It has 3 columns, the first is the package, the second is
    the tag and the remainder of the line is the new value.
  </RefSect1>