Manual.md: add documentation describing repositories and the repository variable.

This commit is contained in:
Enno Boland 2014-11-01 13:41:38 +01:00
parent bf9ea156d8
commit cb7c83f230
1 changed files with 23 additions and 1 deletions

View File

@ -406,7 +406,8 @@ paths, and multiple entries can be separated by blanks, i.e:
- `noarch` If set, the binary package is not architecture specific and can be shared - `noarch` If set, the binary package is not architecture specific and can be shared
by all supported architectures. by all supported architectures.
- `nonfree` If set, the binary package will be put into the *non free* repository. - `repository` Defines the repository in which the package will be placed. See
*Repositories* for a list of valid repositories.
- `nostrip` If set, the ELF binaries with debugging symbols won't be stripped. By - `nostrip` If set, the ELF binaries with debugging symbols won't be stripped. By
default all binaries are stripped. default all binaries are stripped.
@ -435,6 +436,27 @@ pkgver the resulting package should revert. This field *must* be defined before
defined in `reverts` must be lesser than the one defined in `version`. defined in `reverts` must be lesser than the one defined in `version`.
example: `reverts="2.0_1 2.0_2"` example: `reverts="2.0_1 2.0_2"`
#### Repositories
##### Repositories defined by Branch
The global repository takes the name of
the current branch, except if the name of the branch is master. Then the resulting
repository will be at the global scope. The usage scenario is that the user can
update multiple packages in a second branch without polluting his local repository.
##### Package defined Repositories
The second way to define a repository is by setting the `repository` variable in
a template. This way the maintainer can define repositories for a specific
package or a group of packages. This is currently used to distinguish between
closed source packages, which are put in the `nonfree` repository and other
packages which are at the root-repository.
The following repository names are valid:
* `nonfree`: Repository for closed source packages.
#### Checking for new upstream releases #### Checking for new upstream releases
For automatic checking of new versions, in some cases you need to define For automatic checking of new versions, in some cases you need to define