From: "Göktürk Yüksek" <gokturk@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: general-concepts/use-flags/
Date: Wed, 22 May 2019 19:37:26 +0000 (UTC) [thread overview]
Message-ID: <1558553655.ac170fabb913b0818eec678c4be6f1b7a05f8a34.gokturk@gentoo> (raw)
commit: ac170fabb913b0818eec678c4be6f1b7a05f8a34
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Mon Apr 22 19:49:49 2019 +0000
Commit: Göktürk Yüksek <gokturk <AT> gentoo <DOT> org>
CommitDate: Wed May 22 19:34:15 2019 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=ac170fab
general-concepts/use-flags: Explain resolving automagic deps
Explain how developers should resolve automagic deps properly (via
upstream patch), and how they can easily solve it locally (via cache
variables or forcing dep unconditionally).
Suggested-by: Michael Orlitzky <mjo <AT> gentoo.org>
Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>
general-concepts/use-flags/text.xml | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/general-concepts/use-flags/text.xml b/general-concepts/use-flags/text.xml
index 4d56d97..186c51d 100644
--- a/general-concepts/use-flags/text.xml
+++ b/general-concepts/use-flags/text.xml
@@ -27,6 +27,16 @@ dependency is not detected by the package manager tools and can easily
break, among other issues.
</p>
+<p>
+Automagic dependencies are preferably fixed by preparing a build system patch
+adding appropriate options to control the dependency in question, and submitting
+this patch upstream for the benefit of all users. To avoid carrying additional
+patches downstream, automagic dependencies can usually be worked around using
+special build system options (e.g. cache variables in autotools) or through
+depending on the relevant packages unconditionally (i.e. forcing the check
+to always succeed).
+</p>
+
<note>
The status of USE flags is saved in the VDB, and their value in
<c>pkg_prerm</c> and <c>pkg_postrm</c> is taken from there. This means that
next reply other threads:[~2019-05-22 19:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 19:37 Göktürk Yüksek [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-09 18:29 [gentoo-commits] proj/devmanual:master commit in: general-concepts/use-flags/ Ulrich Müller
2023-08-22 6:03 Ulrich Müller
2022-02-21 21:40 Sam James
2021-08-01 2:13 Sam James
2021-08-01 2:08 Sam James
2021-04-10 7:03 Ulrich Müller
2021-04-10 7:03 Ulrich Müller
2021-04-10 7:03 Ulrich Müller
2021-04-02 7:00 Ulrich Müller
2019-05-24 8:40 Ulrich Müller
2019-05-22 19:37 Göktürk Yüksek
2019-05-22 19:37 Göktürk Yüksek
2019-05-22 19:37 Göktürk Yüksek
2019-05-22 19:37 Göktürk Yüksek
2018-06-22 18:25 Ulrich Müller
2014-04-06 15:51 Markos Chandras
2012-04-05 14:22 Torsten Veller
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=1558553655.ac170fabb913b0818eec678c4be6f1b7a05f8a34.gokturk@gentoo \
--to=gokturk@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