Namespace cleanup.

Rename "access method" to "dictionary".
All sources affected.

* src/method.c: renamed to...
* src/dictionary.c: ... this.

16 files changed, 514 insertions, 501 deletions

diff --git a/doc/wydawca.texi b/doc/wydawca.texi
index a136fd6..04b599f 100644
--- a/doc/wydawca.texi
+++ b/doc/wydawca.texi
@@ -92,7 +92,7 @@ How to Configure @command{wydawca}.
 * Syntax::               Configuration file syntax.
 * syslog::
 * sql::
-* access methods::
+* dictionaries::
 * archivation::
 * spool::
 * statistics::
@@ -105,13 +105,13 @@ Configuration file syntax
 * Statements::
 * Preprocessor::
 
-Access Methods
+Dictionaries
 
 * sql type::
 * builtin type::
 * external type::
 
-SQL Access Methods
+SQL Dictionary
 
 * project-owner-sql::
 * project-uploader-sql::
@@ -130,13 +130,13 @@ Mail Notification
 @chapter Introduction to Wydawca
 @cindex introduction
   Let's begin with a short synopsis. Suppose you run a developer's
-site, like, e.g. @indicateurl{gnu.org}. You have at least two
+site, like, e.g. @indicateurl{gnu.org}. You have two
 @dfn{distribution @acronym{URL}s}: @indicateurl{ftp.gnu.org}, which
 distributes stable versions of the software, and
 @indicateurl{alpha.gnu.org}, which distributes alpha and pre-test
-versions. Now, package maintainers should have a way of uploading
-their packages to one of these sites. The currently accepted scheme
-is described in
+versions. Now, package maintainers need to have a way of uploading
+their packages to one of these sites. This is done using the
+@dfn{Automated FTP Upload} method, as described in
 @ifnothtml
 @ref{Automated FTP Uploads, Automated FTP Uploads, Automated FTP
 Uploads, maintain, Information for maintainers of GNU software}.
@@ -157,16 +157,17 @@ corresponding to a certain distribution @acronym{URL}. For example,
 @item @file{/incoming/ftp} @tab @indicateurl{ftp.gnu.org}
 @item @file{/incoming/alpha} @tab @indicateurl{alpha.gnu.org}
 @end multitable
+@*
 
 @cindex @acronym{PGP}
 @cindex detached signature
 @cindex signature, detached
-  Now, if the maintainer of the project @samp{foo} wishes to make a release
+  Now, if maintainer of the project @samp{foo} wishes to make a release
 of the stable version @file{foo-1.0.tar.gz}, he first creates a detached
 signature @file{foo-1.0.tar.gz.sig}. Then he creates a special
-@dfn{directive} file, that contains information about where the
+@dfn{directive} file, which contains information about where the
 distributed tarball must be placed, and clear-signs it using his
-@acronym{PGP} key, thus obtaining file
+@acronym{PGP} key, thus obtaining the file
 @file{foo-1.0.tar.gz.directive.asc}. Finally, he uploads these three files
 (a @dfn{triplet}) to the upload site, storing them into the directory
 @file{/incoming/ftp}.
@@ -179,9 +180,9 @@ their distribution sites.
 
   @command{Wydawca} is such a release submission daemon. It is able to
 handle any number of @samp{source/destination} pairs (called
-@dfn{spools}, offers an extensible logging and mail notification
-mechanism, allowing both package maintainers and site administrators
-to be immediately notified about any occurring problems.
+@dfn{spools}) in real time, and offers an extensible logging and mail
+notification mechanism, allowing both package maintainers and site
+administrators to be immediately notified about any occurring problems.
 
   @command{Wydawca} supports version 1.1 of directory file, as
 described in
@@ -224,7 +225,7 @@ that case.
 upload and corresponding distribution directories. In
 @command{wydawca} terminology, upload directories are also called
 @dfn{source}, and distribution directories -- @dfn{destination}
-directories. The file also supplies all the information 
+directories. The configuration file also supplies all the information 
 necessary to access user and project databases.
 
   When started, @command{wydawca} scans each source directory and
@@ -235,9 +236,9 @@ supplied with each upload and that contains directive regarding the
 placement of the uploaded files. A @dfn{triplet} is a standard
 entity, consisting of three files: a clear-signed directive file, a
 file to be distributed, and a detached signature of the latter.
-In some special cases, a clear-signed directive file alone is valid,
-namely when it contains only @dfn{standalone directives}, as described
-in
+In some special cases, a clear-signed directive file alone is valid.
+This happens when it contains only @dfn{standalone directives}, as
+described in
 @ifnothtml
 @ref{FTP Upload Directive File - v1.1,
 Standalone directives, Standalone directives,
@@ -248,26 +249,38 @@ maintain, Information for maintainers of GNU software}.
 Standalone directives}.
 @end ifhtml
 
-  Each @dfn{incomplete} triplet, i.e. such that misses one or more
+@cindex triplet, incomplete
+@cindex incomplete triplet
+@cindex triplet, expired
+@cindex expired triplet
+  Each @dfn{incomplete} triplet, i.e. a triplet missing one or more
 necessary files, is then verified by checking if the modification
 date of its oldest file is older than a predefined amount of time
-(@FIXME-pxref{file-sweep-time}), and if so, all files from this triplet are
-removed (an @dfn{expired triplet}). This gives users the possibility
-to restart interrupted or otherwise broken uploads later.
-
-  Then, the utility ensures that each of the remaining triplets is
-created by a single person. Any triplets that do not are immediately
-removed.
+(@FIXME-pxref{file-sweep-time}). If so, the triplet is considered
+@dfn{expired}, and all its files are removed. This gives users the
+possibility to restart interrupted or otherwise broken uploads later.
 
+@cindex dictionary
 @cindex @acronym{PGP}
+  After completing these preliminary stages, @command{wydawca}
+analyzes the directive file and extracts the project name
+from it. Using this name as a key, it looks up in the @dfn{project
+dictionary} a list of users authorized to make uploads for this
+project. This list contains user names and their corresponding public
+@acronym{PGP} keys. @command{Wydawca} tries to verify the directive
+file using each @acronym{PGP} key from this list, until a matching
+key is found, or the list in exhausted. In the latter case, the
+triplet is rejected. Otherwise, the key and its owner are remembered
+for the next step.
+
+@cindex detached signature
 @cindex detached signature
 @cindex signature, detached
-  Then, @acronym{PGP} signatures of directive files and any detached
-signatures (if available) are verified. If they do not match public
-keys of the user who uploaded the triplet, such a triplet is
-discarded.
+  In this step, the uploaded file and its detached signature
+are verified. If they do not match the public key obtained in the
+previous step, the triplet is rejected.
 
-  Finally, the directives from each directive file are executed. On
+  Finally, directives from the directive file are executed. On
 this stage of the processing, the uploaded files are actually moved to
 their destination directories, requested symbolic links are created,
 etc.
@@ -387,7 +400,7 @@ directives any time by running @command{wydawca --config-help}.
 * Syntax::               Configuration file syntax.
 * syslog::
 * sql::
-* access methods::
+* dictionaries::
 * archivation::
 * spool::
 * statistics::
@@ -860,7 +873,7 @@ sql @var{id} @{
 
   Here, @var{id} is a string uniquely identifying this
 database. It is used by another configuration statements (e.g. by
-access methods, see the next section) to refer to this
+dictionaries, see the next section) to refer to this
 database. 
 @end deffn
 
@@ -904,21 +917,21 @@ sql default @{