Release Submission Daemon
Let’s begin with a short synopsis. Suppose you run a developer’s
site, such as e.g. ‘
gnu.org’. You have two
distribution URLs: ‘
distributes stable versions of the software, and
alpha.gnu.org’, which distributes alpha and pre-test
versions. Package maintainers need a way of uploading
their packages to one of these sites. This is done using the
Automated FTP Upload method described in
Automated Upload Procedure.
The following is a short summary of it: there is an FTP
upload site, which has two source directories, each one
corresponding to a certain distribution URL. For example,
|Source Directory||Distribution Site|
If maintainer of the project ‘foo’ wishes to make a release of the stable version foo-1.0.tar.gz, he first creates a detached signature foo-1.0.tar.gz.sig. Then he creates a special directive file, which contains information about where the distributed tarball must be placed, and clear-signs it using his PGP key, thus obtaining the file foo-1.0.tar.gz.directive.asc. Finally, he uploads these three files (a triplet) to the upload site, storing them into the directory /incoming/ftp.
From now on, it is the responsibility of a release submission daemon to scan source directories, gather triplets, verify them, and to move any files that had successfully passed verification to their distribution sites.
Wydawca is such a release submission daemon. It is able to
handle any number of ‘source/destination’ pairs (called
spools) in real time, and offers extensible logging and
notification mechanisms, allowing both package maintainers and site
administrators to be immediately notified about any occurring problems.
Wydawca supports upload directive versions 1.11 and 1.22.
The program is written entirely in C, is highly effective and consumes little resources.
This document was generated on January 6, 2021 using makeinfo.Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.