6 Tarballs

Any word in the command line that is not an argument to a preceding option specifies a release tarball for upload. Normally, tarballs are located in the current working directory. However, it is not required: they can reside anyplace on the local filesystem. The directory part is stripped off the tarball name before creating the filename: stanza in the directive file. Thus, the created directive will instruct upload server to place the file to the top-level directory of the project. For example, if you run

grayupload --to alpha.gnu.org:foo build/foo-0.1.tar.gz

then, as a result of the upload, the file build/foo-0.1.tar.gz will appear in ‘https://alpha.gnu.org/gnu/foo/’. Most servers allow uploaders to create any directory hierarchy your their package directory. If you do wish to upload your tarballs to a subdirectory, give its name in the destination specification, for example:

grayupload --to alpha.gnu.org:foo/temp build/foo-0.1.tar.gz

The subdirectory will be created if it doesn’t exist.

Notice, that grayupload creates signature and directive files in the directory where the tarball is located. This means, obviously, that this directory must be writable.

Created signature files remain on disk after termination of the program. You may need these for other tasks related to the release. In contrast, directive files are always removed. If you wish to inspect their content, use two -v options.