From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: general-concepts/dependencies/
Date: Mon, 29 Mar 2021 20:44:05 +0000 (UTC) [thread overview]
Message-ID: <1617050498.a0af214749946a602a8fef95495ca9150bf93946.ulm@gentoo> (raw)
commit: a0af214749946a602a8fef95495ca9150bf93946
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Mar 20 14:56:44 2021 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Mon Mar 29 20:41:38 2021 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=a0af2147
general-concepts/dependencies: emphasise BDEPEND for build-system dependencies
Signed-off-by: Sam James <sam <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
general-concepts/dependencies/text.xml | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/general-concepts/dependencies/text.xml b/general-concepts/dependencies/text.xml
index eac1967..f49e319 100644
--- a/general-concepts/dependencies/text.xml
+++ b/general-concepts/dependencies/text.xml
@@ -626,12 +626,13 @@ package:
</dd>
<dt>
Remember non-binary dependencies such as pkg-config, doc generation
- programs, etc.
+ programs, etc. Such programs would usually belong in <c>BDEPEND</c>.
</dt>
<dd>
Usually the build process requires some dependencies such as intltool,
libtool, pkg-config, doxygen, scrollkeeper, gtk-doc, etc. Make sure those
- are clearly stated.
+ are clearly stated. Again, such dependencies usually belong in
+ <c>BDEPEND</c>.
</dd>
</dl>
next reply other threads:[~2021-03-29 20:44 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 20:44 Ulrich Müller [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-28 19:36 [gentoo-commits] proj/devmanual:master commit in: general-concepts/dependencies/ Ulrich Müller
2023-09-27 8:30 Ulrich Müller
2022-06-24 9:14 Ulrich Müller
2022-05-27 9:00 Ulrich Müller
2022-05-22 6:37 Joonas Niilola
2022-05-22 6:37 Joonas Niilola
2022-02-21 5:22 Sam James
2022-02-21 5:22 Sam James
2021-10-19 9:27 Mike Frysinger
2021-10-13 13:42 Ulrich Müller
2021-03-29 20:44 Ulrich Müller
2021-03-29 20:44 Ulrich Müller
2021-03-11 12:44 Ulrich Müller
2021-03-11 12:44 Ulrich Müller
2021-03-11 12:44 Ulrich Müller
2020-05-25 15:43 Ulrich Müller
2020-05-25 15:43 Ulrich Müller
2020-01-29 7:59 Ulrich Müller
2020-01-29 7:59 Ulrich Müller
2020-01-29 7:59 Ulrich Müller
2020-01-23 7:47 Ulrich Müller
2019-12-21 5:19 Ulrich Müller
2019-10-16 18:49 Göktürk Yüksek
2018-09-10 15:20 Mike Gilbert
2017-09-25 4:31 Göktürk Yüksek
2017-09-25 4:31 Göktürk Yüksek
2017-09-25 4:31 Göktürk Yüksek
2014-10-18 17:40 Markos Chandras
2013-07-29 21:53 Julian Ospald
2013-07-29 21:53 Julian Ospald
2011-02-17 21:08 Jeremy Olexa
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=1617050498.a0af214749946a602a8fef95495ca9150bf93946.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