2 Quick Start

The interface of grayupload is deliberately designed to be as close as possible to that of gnuplod, so that in most cases it can be used as a drop-in replacement for the latter. Suppose a programmer maintains a package called ‘foo’ and distributes its tarballs from ‘https://download.gnu.org.ua/release/foo’. This means that the project is already registered, and the programmer has already uploaded his public GPG key to its account on ‘puszcza.gnu.org.ua’.

Now, to upload a new release (say foo-1.0.tar.gz), the programmer would run:

grayupload --to download.gnu.org.ua:ftp/foo foo-1.0.tar.gz

To create the symlink foo-latest.tar.gz, pointing to the newly uploaded file, he would run instead:

grayupload --to download.gnu.org.ua:ftp/foo --latest foo-1.0.tar.gz

Supposing the file foo-0.9.tar.gz is already available from the distribution server, one can create a symbolic link foo-prior.tar.gz pointing to it, by running

grayupload --to download.gnu.org.ua:ftp/foo \
           --symlink foo-0.9.tar.gz foo-prior.tar.gz

To remove an obsolete or broken tarball foo-0.1.tar.gz from the distribution server, one would run

grayupload --to download.gnu.org.ua:ftp/foo --delete foo-0.1.tar.gz

Similarly, if the distribution tarballs were distributed on ‘ftp.gnu.org’, the --to option in the examples above would have been rewritten as:

--to ftp.gnu.org:foo

These and other grayupload options are discussed in detail in the rest of this document.