From: "Göktürk Yüksek" <gokturk@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: function-reference/install-functions/
Date: Mon, 28 Aug 2017 20:01:55 +0000 (UTC) [thread overview]
Message-ID: <1503950420.dd8078107236415fd8c5ea461f0119dd1e285a4c.gokturk@gentoo> (raw)
commit: dd8078107236415fd8c5ea461f0119dd1e285a4c
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sat Aug 26 17:08:23 2017 +0000
Commit: Göktürk Yüksek <gokturk <AT> gentoo <DOT> org>
CommitDate: Mon Aug 28 20:00:20 2017 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=dd807810
install-functions: Verbosely explain dosym target parameter
It is a common misconception that dosym takes two paths, both of them
interpreted relatively to ${ED}. To avoid that, explicitly explain
that the first parameter is interpreted as a verbatim symlink target.
function-reference/install-functions/text.xml | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/function-reference/install-functions/text.xml b/function-reference/install-functions/text.xml
index 6523521..c1392bf 100644
--- a/function-reference/install-functions/text.xml
+++ b/function-reference/install-functions/text.xml
@@ -257,7 +257,11 @@ the first is the source name, the second the name to use when installing.
<c>dosym</c>
</ti>
<ti>
- Create a symlink from the second parameter to the first parameter
+ Create a symlink to the target specified as the first parameter,
+ at the path specified by the second parameter. Note that
+ the target is interpreted <e>verbatim</e>; it needs to either
+ specify a relative path or an absolute path including
+ <c>${EPREFIX}</c>.
</ti>
</tr>
<tr>
next reply other threads:[~2017-08-28 20:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 20:01 Göktürk Yüksek [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-21 19:06 [gentoo-commits] proj/devmanual:master commit in: function-reference/install-functions/ Ulrich Müller
2023-05-27 18:51 Ulrich Müller
2023-04-29 15:29 Ulrich Müller
2022-01-17 16:52 Ulrich Müller
2020-02-24 8:14 Ulrich Müller
2019-11-22 22:45 Michael Orlitzky
2018-10-24 13:01 Brian Evans
2018-10-24 13:01 Brian Evans
2018-08-01 22:59 Göktürk Yüksek
2018-06-22 18:25 Ulrich Müller
2017-06-21 17:28 Göktürk Yüksek
2016-12-08 16:47 Göktürk Yüksek
2016-12-07 19:46 Göktürk Yüksek
2016-12-07 19:46 Göktürk Yüksek
2016-11-30 5:29 Göktürk Yüksek
2016-10-04 12:02 Göktürk Yüksek
2016-10-03 14:52 Ulrich Müller
2016-10-03 14:52 Ulrich Müller
2016-10-03 13:45 Mike Gilbert
2016-08-18 3:26 Göktürk Yüksek
2013-02-10 3:26 Mike Gilbert
2012-11-07 13:43 Michael Palimaka
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=1503950420.dd8078107236415fd8c5ea461f0119dd1e285a4c.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