Next: Release types, Previous: Debugging, Up: Top [Contents][Index]
If the file .grayupload exists in the current working directory, the program reads its options from it.
The lines in configuration file are processed sequentially. Empty lines are ignored. The ‘#’ character starts inline comment: the character itself and all characters that follow it up to the end of line are ignored.
A non-empty file must consist of a keyword and value separated by any amount of whitespace. Leading and trailing whitespace is removed. If the value includes whitespace or comment characters, it should be enclosed in double quotes. Within double-quotes a backslash character serves as an escape indicator: it is removed and the character that follows it is taken literally. This allows for embedding double quotes (‘\"’) and backslashes (‘\\’) in quoted strings.
Allowed keywords correspond to option names without leading dash:
Defines destination location. Argument must be one of standard destinations (see Standard destinations). It can optionally be prefixed with ‘type=’ to indicate that it is to be used only for the given release type. See Release types, for a detailed discussion of this useful feature.
The --to and --url command line options override this setting.
Defines destination URL. See upload url, for a discussion of dest syntax. The URL can optionally be prefixed with ‘type=’ to indicate that it is to be used only for the given release type. See Release types, for a detailed discussion of this useful feature.
Sets the default destination directory name, This name will be used
for any subsequent url statement that doesn’t specify
destination directory explicitly.
Sign tarballs and directives with the GPG key id.
Add comment text to the directive. By default, single comment
is added specifying the name and version of the program that did the
upload. Multiple comment statements are allowed. Eventual
--comment command line options don’t override, but rather
append their arguments to the list of comments created by the
comment statements.
If text contains whitespace, double quotes or backslash characters, it must be enclosed in a pair of double quotes (and embedded double quotes or comments escaped as described at the beginning of this chapter).
Set verbosity level. Allowed values for number are 0 through 3.
Version semantics defines the algorithm used to determine release type from version number. It is used if release type is not specified explicitly in the command line.
Possible values for the name argument are gnu and
kernel. If version semantics is set to gnu, version
numbers consisting of major and minor parts imply ‘stable’
release. If the version number has patch-level part, and this part
is numerically greater than or equal to 90, then ‘alpha’ release
is assumed. Otherwise, the version indicates ‘stable’ release.
If name is kernel, then major part of the release number
determines the release type. If it is even, then it is a
‘stable’ release. Otherwise, it is a ‘alpha’ release.
See Version semantics, for a detailed discussion of this feature.
If bool is ‘true’, then, for each file uploaded to the server, create the latest symlink. See Creating symlinks, for details.
Allowed bool values are true, on, yes,
1, for ‘true’ and false, off, no, and
0, for ‘false’.
For each uploaded file, create a symlink, with the
name obtained by applying a sed expression s-exp
to the file name. See Creating symlinks, for details.
If a tarball already exists on the distribution server, replace it with
the supplied one. See the description of the latest statement
for the list of allowed values for bool.
Command line options override the corresponding configuration
statements. For example, if your .grayupload file contains
three to statements and you supply a --to option in
the command line, these configuration statements are ignored and the
destination supplied in the command line is used instead.
To supply alternative configuration file, use the --config file option. If given, file will be read, instead of .grayupload. Notice, that file must exist.
To ignore existing configuration file, use the --no-config option.
Next: Release types, Previous: Debugging, Up: Top [Contents][Index]