commit: 87ea31e871d19af32750bdd187a84589cffd329b Author: Ulrich Müller <ulm <AT> gentoo <DOT> org> AuthorDate: Tue Mar 24 12:10:05 2020 +0000 Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org> CommitDate: Tue Mar 24 12:10:05 2020 +0000 URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=87ea31e8
ebuild-writing/file-format: New subsection for binary packages. Discussion reference: https://archives.gentoo.org/gentoo-dev/message/8dadfbd3c15b6580abb84882e9115a47 and replies. Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org> ebuild-writing/file-format/text.xml | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/ebuild-writing/file-format/text.xml b/ebuild-writing/file-format/text.xml index 16d857e..5eb0cf8 100644 --- a/ebuild-writing/file-format/text.xml +++ b/ebuild-writing/file-format/text.xml @@ -140,6 +140,27 @@ The policy for so-called <e>live</e> ebuilds is to use <c>9999</c> as the version (or as the last version component). </p> +</body> +</subsection> + +<subsection> +<title>Binary packages</title> +<body> + +<p> +Gentoo usually builds its packages from source. Exceptionally, a binary package +can be provided instead (e.g., if upstream does not provide a source). +Such packages should still follow normal naming conventions and do not need any +special suffix. +</p> + +<p> +If a binary package is provided in addition to its open-source based +equivalent, the name of the former should be suffixed with <c>-bin</c> +if necessary for distinction. Examples are packages that are heavy on resources +like CPU time or memory when being built from source. +</p> + </body> </subsection> </section>
