1 |
>>>>> On Sun, 22 Dec 2019, Michał Górny wrote: |
2 |
|
3 |
> --- a/appendices.tex |
4 |
> +++ b/appendices.tex |
5 |
|
6 |
Hm, we list retroactive fixes in the appendix only if we go through |
7 |
Council approval. I wonder if we need it for this, when the |
8 |
functionality was never actually used? |
9 |
|
10 |
> @@ -110,6 +110,13 @@ all-of, any-of, exactly-one-of, at-most-one-of and use-conditional groups with z |
11 |
> However, such empty groups were neither supported by all package managers nor used in ebuilds. |
12 |
> They were dropped from the specification in October 2017. |
13 |
> |
14 |
> +\subsection{Simple filename in SRC\_URI} |
15 |
|
16 |
No backslash before the underscore please, it will break grepping for |
17 |
SRC_URI. |
18 |
|
19 |
> +The SRC\_URI format (see section~\ref{sec:src-uri-behaviour}) originally permitted using a simple |
20 |
> +filename instead of a full URI to indicate a~file that can be fetched from mirrors only. |
21 |
> +However, the Portage implementation worked only if the user had configured mirrors explicitly, |
22 |
> +and it was not used in ebuilds. This feature has been dropped in December 2019, limiting simple |
23 |
|
24 |
Nitpick, please use a single space after the full stop, for consistency |
25 |
throughout the document. |
26 |
|
27 |
> +filename usage to fetch-restricted packages. |
28 |
> + |
29 |
> % vim: set filetype=tex fileencoding=utf8 et tw=100 spell spelllang=en : |
30 |
> |
31 |
> %%% Local Variables: |
32 |
|
33 |
> --- a/ebuild-vars.tex |
34 |
> +++ b/ebuild-vars.tex |
35 |
> @@ -159,11 +159,9 @@ managers may also consult mirrors for their files. |
36 |
> The special \t{mirror://} protocol must be supported. See section~\ref{sec:thirdpartymirrors} for |
37 |
> mirror details. |
38 |
> |
39 |
> -If a simple filename rather than a full URI is provided, the package manager can only use mirrors |
40 |
> -to download the file. |
41 |
> - |
42 |
> The \t{RESTRICT} metadata key can be used to impose additional restrictions upon downloading---see |
43 |
> -section~\ref{sec:restrict} for details. |
44 |
> +section~\ref{sec:restrict} for details. If a fetch restriction is used, a simple filename can |
45 |
> +be used in lieu of full URI. |
46 |
|
47 |
"Lieu"? Merriam-Webster labels this as archaic. Also usage of the |
48 |
indefinite articles in that sentence is a little odd. |
49 |
|
50 |
Suggestion: "Fetch restricted packages may use a simple filename instead |
51 |
of a full URI." |
52 |
|
53 |
> |
54 |
> \featurelabel{src-uri-arrows} In EAPIs listed in table~\ref{tab:uri-arrows-table} as supporting |
55 |
> arrows, if an arrow is used, the filename used when saving to \t{DISTDIR} shall instead be the name |
56 |
|
57 |
Ulrich |