diff options
| author |   Jauhien Piatlicki (jauhien) <piatlicki@gmail.com> | 2013-09-20 01:22:37 +0200 |
|---|---|---|
| committer | Jauhien Piatlicki (jauhien) <piatlicki@gmail.com> | 2013-09-20 01:22:37 +0200 |
| commit | e08af5649fd7b68b5fb44e37e0c468686c7cab39 (patch) | |
| tree | 711fb2eb9e649bc20196ea25cb5e1b01f6705fb0 | |
| parent | README actualized (diff) | |
| download | g-sorcery-e08af5649fd7b68b5fb44e37e0c468686c7cab39.tar.gz g-sorcery-e08af5649fd7b68b5fb44e37e0c468686c7cab39.tar.bz2 g-sorcery-e08af5649fd7b68b5fb44e37e0c468686c7cab39.zip | |
README: fix
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -68,7 +68,7 @@ usual. It's all you need to do and it's the recommended way of using **g-sorcery**. Using **g-sorcery** with layman you can populate overlay only with packages you want. -To do so you should add a section named [BACKEND] (BACKEND here is the name of backend used for +To do so you should add a section named BACKEND (BACKEND here is the name of backend used for your repo). In this section you can add entries named REPO_packages (REPO here is the name of repository you want to add) which are space separated list of packages you need. ebuilds for dependencies will be generated automatically if backend supports this possibility. |