<simpara
  >&config.OS.NAME; uses its very own package format.
  Installing a package also puts a text file describing the package
  in directory <filename>/var/log/packages/</filename>. 
  There is no index and no tool to make queries.
</simpara>

<formalpara>
  <title>Source: &config.PRE;/packages/slackware/du.sh</title>
  <para>
    <programlisting><inlinemediaobject><imageobject><imagedata
      format="linespecific"
      fileref="../../&config.PRE;/packages/slackware/du.sh"
    /></imageobject></inlinemediaobject></programlisting>
  </para>
</formalpara>
<formalpara>
  <title>Output: &config.OUT;/packages/du</title>
  <para>
    <programlisting><inlinemediaobject><imageobject><imagedata
      format="linespecific"
      fileref="../../&config.OUT;/packages/du"
    /></imageobject></inlinemediaobject></programlisting>
  </para>
</formalpara>

<simpara
  >File names are stored without leading slash. The rest of
  the query is good old (i.e. slow) text processing.
</simpara>

<formalpara>
  <title>Source: &config.PRE;/packages/slackware/simple.sh</title>
  <para>
    <programlisting><inlinemediaobject><imageobject><imagedata
      format="linespecific"
      fileref="../../&config.PRE;/packages/slackware/simple.sh"
    /></imageobject></inlinemediaobject></programlisting>
  </para>
</formalpara>
<formalpara>
  <title>Output: &config.OUT;/packages/simple</title>
  <para>
    <programlisting><inlinemediaobject><imageobject><imagedata
      format="linespecific"
      fileref="../../&config.OUT;/packages/simple"
    /></imageobject></inlinemediaobject></programlisting>
  </para>
</formalpara>

<simpara
  >The package description holds no separate version field.
  But by convention the last three segments (separated by slash)
  of a package name have a fixed meaning, as explained by comments
  in shell script <filename>/sbin/upgradepkg</filename>.
</simpara>
