|
Lines 14-20
names will contain a hyphen.
Link Here
|
| 14 |
|
14 |
|
| 15 |
\subsection{Package Names} |
15 |
\subsection{Package Names} |
| 16 |
A package name may contain any of the characters [\t{A-Za-z0-9+\_-}]. It must not begin with a |
16 |
A package name may contain any of the characters [\t{A-Za-z0-9+\_-}]. It must not begin with a |
| 17 |
hyphen or a plus sign, and must not end in a hyphen followed by one or more digits. |
17 |
hyphen or a plus sign, and must not end in a hyphen followed by anything matching the version |
|
|
18 |
syntax described in section~\ref{sec:version-spec}. |
| 18 |
|
19 |
|
| 19 |
\note A package name does not include the category. The term \i{qualified package name} is used |
20 |
\note A package name does not include the category. The term \i{qualified package name} is used |
| 20 |
where a \t{category/package} pair is meant. |
21 |
where a \t{category/package} pair is meant. |
|
Lines 48-53
An EAPI name may contain any of the characters [\t{A-Za-z0-9+\_.-}]. It must not
Link Here
|
| 48 |
hyphen, a dot or a plus sign. |
49 |
hyphen, a dot or a plus sign. |
| 49 |
|
50 |
|
| 50 |
\section{Version Specifications} |
51 |
\section{Version Specifications} |
|
|
52 |
\label{sec:version-spec} |
| 51 |
The package manager must not impose fixed limits upon the number of version components. Package |
53 |
The package manager must not impose fixed limits upon the number of version components. Package |
| 52 |
managers should indicate or reject any version that is invalid according to these rules. |
54 |
managers should indicate or reject any version that is invalid according to these rules. |
| 53 |
|
55 |
|
| 54 |
- |
|
|
