From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/file-format/
Date: Sat, 28 Mar 2020 14:47:16 +0000 (UTC) [thread overview]
Message-ID: <1585051805.87ea31e871d19af32750bdd187a84589cffd329b.ulm@gentoo> (raw)
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>
next reply other threads:[~2020-03-28 14:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-28 14:47 Ulrich Müller [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-21 7:49 [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/file-format/ Ulrich Müller
2023-01-12 11:27 Joonas Niilola
2021-08-14 1:46 Sam James
2021-08-14 1:46 Sam James
2021-03-30 16:10 Ulrich Müller
2021-03-30 16:10 Ulrich Müller
2021-03-30 7:32 Ulrich Müller
2021-03-30 7:32 Ulrich Müller
2020-03-28 14:47 Ulrich Müller
2019-06-23 18:13 Ulrich Müller
2019-06-23 18:13 Ulrich Müller
2017-11-12 20:37 Ulrich Müller
2017-03-03 5:54 Ulrich Müller
2016-11-22 5:45 Göktürk Yüksek
2016-11-03 15:25 Göktürk Yüksek
2015-08-09 9:30 Justin Lecher
2015-05-09 15:22 Ulrich Müller
2015-04-15 6:42 Ulrich Müller
2014-10-18 17:35 Markos Chandras
2014-07-24 18:06 ` Markos Chandras
2014-07-24 18:06 Markos Chandras
2014-10-18 17:35 ` Markos Chandras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1585051805.87ea31e871d19af32750bdd187a84589cffd329b.ulm@gentoo \
--to=ulm@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox