diff options
| author |   Michał Górny <mgorny@gentoo.org> | 2019-10-06 10:11:57 +0200 |
|---|---|---|
| committer |   Göktürk Yüksek <gokturk@gentoo.org> | 2019-10-16 15:54:13 -0400 |
| commit | 2ee6d48917ae4c7646248fd2ad4e071fa2bbe6cd (patch) | |
| tree | f4d42d5d26ae6d4e973772cc97a8ef56d8f2f4a1 /ebuild-writing | |
| parent | ebuild-writing/variables: Update the thirdpartymirrors example (diff) | |
| download | devmanual-2ee6d48917ae4c7646248fd2ad4e071fa2bbe6cd.tar.gz devmanual-2ee6d48917ae4c7646248fd2ad4e071fa2bbe6cd.tar.bz2 devmanual-2ee6d48917ae4c7646248fd2ad4e071fa2bbe6cd.zip | |
ebuild-writing/variables: Reindent section on mirror://
No text changes, just reformatting to the currently used style.
Acked-by: Michael Orlitzky <mjo@gentoo.org>
Signed-off-by: Michał Górny <mgorny@gentoo.org>
Signed-off-by: Göktürk Yüksek <gokturk@gentoo.org>
Diffstat (limited to 'ebuild-writing')
| -rw-r--r-- | ebuild-writing/variables/text.xml | 68 |
1 files changed, 36 insertions, 32 deletions
diff --git a/ebuild-writing/variables/text.xml b/ebuild-writing/variables/text.xml index a66adc7..23e423c 100644 --- a/ebuild-writing/variables/text.xml +++ b/ebuild-writing/variables/text.xml @@ -399,22 +399,25 @@ SRC_URI="https://example.com/files/${PV}.tar.gz -> ${P}.tar.gz" <subsection> - <title>Third-party mirrors</title> - <body> - <p> - If the items in <c>SRC_URI</c> are available on multiple - third-party mirrors, then you don't have to list each mirror in - your ebuild. The <c>profiles/thirdpartymirrors</c> file in the - <c>::gentoo</c> repository contains named groups of mirrors, - accessible through the <c>mirror://</c> pseudo-protocol. - </p> - <p> - As of EAPI 7, the format of <uri - link="https://projects.gentoo.org/pms/7/pms.html#x1-340004.4.2">the - thirdpartymirrors file</uri> is described in section 4.4.2 of - the Package Manager Specification (PMS). One might define a set - of "example" mirrors, - </p> +<title>Third-party mirrors</title> +<body> + +<p> +If the items in <c>SRC_URI</c> are available on multiple third-party mirrors, +then you don't have to list each mirror in your ebuild. +The <c>profiles/thirdpartymirrors</c> file in the <c>::gentoo</c> repository +contains named groups of mirrors, accessible through the <c>mirror://</c> +pseudo-protocol. +</p> + +<p> +As of EAPI 7, the format of <uri +link="https://projects.gentoo.org/pms/7/pms.html#x1-340004.4.2">the +thirdpartymirrors file</uri> is described in section 4.4.2 of the Package +Manager Specification (PMS). One might define a set of "example" +mirrors, +</p> + <!-- The following isn't ebuild code, but lang="ebuild" works, and no other language choice would be accurate either. @@ -422,25 +425,26 @@ SRC_URI="https://example.com/files/${PV}.tar.gz -> ${P}.tar.gz" <codesample lang="ebuild"> example https://download.example.com https://mirror1.example.org/example </codesample> - <p> - that can afterwards be referenced through a <c>mirror://</c> - URL: - </p> + +<p> +that can afterwards be referenced through a <c>mirror://</c> URL: +</p> + <codesample lang="ebuild"> SRC_URI="mirror://example/${PN}/${P}.tar.gz" </codesample> - <warning> - If the sources for a package are neither mirror-restricted nor - fetch-restricted, then they will be <uri - link="::general-concepts/mirrors">mirrored onto Gentoo - infrastructure</uri> automatically; in that case, there is - little benefit to using this feature. There is a maintenance - burden associated with using a third-party mirror list: it must - be updated when new mirrors are born and when old mirrors - die. Please consider that when deciding whether or not to use - this feature. - </warning> - </body> + +<warning> +If the sources for a package are neither mirror-restricted nor +fetch-restricted, then they will be <uri +link="::general-concepts/mirrors">mirrored onto Gentoo infrastructure</uri> +automatically; in that case, there is little benefit to using this feature. +There is a maintenance burden associated with using a third-party mirror list: +it must be updated when new mirrors are born and when old mirrors die. Please +consider that when deciding whether or not to use this feature. +</warning> + +</body> </subsection> </section> |