From 4fa052033a8c9a908339dfa2cfefd281a1493892 Mon Sep 17 00:00:00 2001 From: classabbyamp Date: Mon, 2 Oct 2023 03:19:49 -0400 Subject: [PATCH] Manual.md: mention other valid `repository`s --- Manual.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/Manual.md b/Manual.md index 21162641e47..667ab634f97 100644 --- a/Manual.md +++ b/Manual.md @@ -859,12 +859,14 @@ update multiple packages in a second branch without polluting his local reposito 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. +certain classes of packages. The following repository names are valid: -* `nonfree`: Repository for closed source packages. +* `bootstrap`: Repository for xbps-src-specific packages. +* `debug`: Repository for packages containing debug symbols. In almost all cases, + these packages are generated automatically. +* `nonfree`: Repository for packages that are closed source or have nonfree licenses. ### Checking for new upstream releases