From: "Jeremy Olexa" <darkside@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/common-mistakes/
Date: Wed, 9 Mar 2011 16:42:41 +0000 (UTC) [thread overview]
Message-ID: <4d025023b322d0f82f49143a3164a3d0c176485d.darkside@gentoo> (raw)
commit: 4d025023b322d0f82f49143a3164a3d0c176485d
Author: Jeremy Olexa <darkside <AT> gentoo <DOT> org>
AuthorDate: Wed Mar 9 16:37:45 2011 +0000
Commit: Jeremy Olexa <darkside <AT> gentoo <DOT> org>
CommitDate: Wed Mar 9 16:37:45 2011 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/devmanual.git;a=commit;h=4d025023
common-mistakes: Add section about ROOT
Patch by Thilo Bangert, bug 258125
---
ebuild-writing/common-mistakes/text.xml | 16 ++++++++++++++++
1 files changed, 16 insertions(+), 0 deletions(-)
diff --git a/ebuild-writing/common-mistakes/text.xml b/ebuild-writing/common-mistakes/text.xml
index 8fda324..d2f5fcf 100644
--- a/ebuild-writing/common-mistakes/text.xml
+++ b/ebuild-writing/common-mistakes/text.xml
@@ -21,6 +21,22 @@ the dynamic and static libraries.
</section>
<section>
+<title>Invalid use of <c>ROOT</c></title>
+<body>
+<p>
+The usage of <c>ROOT</c> is only designed to influence the way the package is
+installed (ie. into <c>ROOT</c>) - building and compiling should not depend on
+<c>ROOT</c>. As a consequence of this the usage of <c>ROOT</c> in <c>src_*</c>
+functions is not allowed.
+</p>
+
+<p>
+See also <uri link="::ebuild-writing/variables#ROOT"/>.
+</p>
+</body>
+</section>
+
+<section>
<title>Referencing the full path to documentation files that could be
compressed</title>
<body>
next reply other threads:[~2011-03-09 16:42 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 16:42 Jeremy Olexa [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-08-08 19:20 [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/common-mistakes/ Markos Chandras
2012-11-07 13:25 Michael Palimaka
2012-11-07 13:27 Michael Palimaka
2012-11-11 19:33 Markos Chandras
2012-11-17 19:00 Markos Chandras
2012-11-23 18:02 Julian Ospald
2012-12-04 19:26 Julian Ospald
2012-12-30 14:21 Julian Ospald
2013-09-28 12:19 Markos Chandras
2014-05-13 19:32 Ulrich Müller
2014-10-18 17:36 Markos Chandras
2016-02-05 12:59 Ulrich Müller
2016-10-28 17:13 Ulrich Müller
2017-01-21 19:21 Göktürk Yüksek
2017-01-25 5:31 Göktürk Yüksek
2017-01-25 5:31 Göktürk Yüksek
2021-02-06 10:35 Ulrich Müller
2021-03-21 6:06 Ulrich Müller
2021-03-29 20:44 Ulrich Müller
2021-03-30 16:10 Ulrich Müller
2021-03-30 16:10 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:20 Ulrich Müller
2021-08-01 2:38 Sam James
2021-08-01 2:38 Sam James
2021-08-01 2:38 Sam James
2021-08-01 2:38 Sam James
2021-08-01 2:38 Sam James
2021-08-01 2:43 Sam James
2021-08-14 10:00 Ulrich Müller
2021-09-17 9:09 Ulrich Müller
2021-12-22 15:38 Ulrich Müller
2022-01-22 23:43 Sam James
2024-07-24 14:15 Ulrich Müller
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=4d025023b322d0f82f49143a3164a3d0c176485d.darkside@gentoo \
--to=darkside@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