| 1 |
By requiring repository names to also be valid package names, a package |
| 2 |
mangler may treat repositories as packages. This then allows, for |
| 3 |
example, a user to 'install' a repository, which would instruct the |
| 4 |
package manager to perform the relevant configuration (including |
| 5 |
installing any masters) and syncing. |
| 6 |
--- |
| 7 |
names.tex | 2 +- |
| 8 |
1 files changed, 1 insertions(+), 1 deletions(-) |
| 9 |
|
| 10 |
diff --git a/names.tex b/names.tex |
| 11 |
index 67054c1..c99ed0f 100644 |
| 12 |
--- a/names.tex |
| 13 |
+++ b/names.tex |
| 14 |
@@ -34,7 +34,7 @@ described in section~\ref{sec:use-iuse-handling}. |
| 15 |
\subsection{Repository Names} |
| 16 |
\label{sec:repository-names} |
| 17 |
A repository name may contain any of the characters [\t{A-Za-z0-9\_-}]. It must not begin with a |
| 18 |
-hyphen. |
| 19 |
+hyphen. In addition, every repository name must also be a valid package name. |
| 20 |
|
| 21 |
\subsection{Keyword Names} |
| 22 |
\label{sec:keyword-names} |
| 23 |
-- |
| 24 |
1.7.5.4 |
Archives