From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: function-reference/install-functions/
Date: Sat, 29 Apr 2023 15:29:05 +0000 (UTC) [thread overview]
Message-ID: <1682781978.caa3e98b1431ceeead2924302bcc997d6214ba69.ulm@gentoo> (raw)
commit: caa3e98b1431ceeead2924302bcc997d6214ba69
Author: matoro <matoro <AT> users <DOT> noreply <DOT> github <DOT> com>
AuthorDate: Thu Apr 27 19:07:06 2023 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Sat Apr 29 15:26:18 2023 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=caa3e98b
function-reference/install-functions: add note about paths to dostrip
Found this extremely unintuitive especially compared to the
documentation on the `dosym` function which is much clearer.
Closes: https://bugs.gentoo.org/888817
Signed-off-by: Matoro Mahri <matoro <AT> users.noreply.github.com>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
function-reference/install-functions/text.xml | 1 +
1 file changed, 1 insertion(+)
diff --git a/function-reference/install-functions/text.xml b/function-reference/install-functions/text.xml
index 9fbdcbe..6961784 100644
--- a/function-reference/install-functions/text.xml
+++ b/function-reference/install-functions/text.xml
@@ -431,6 +431,7 @@ The <c>*into</c> functions create the directory if it does not already exist.
Normally executed to exclude from stripping.
Eg. <c>dostrip -x /path/to/important.so</c>. May also be used to include binaries
to strip when <c>RESTRICT=strip</c> without the -x option.
+ Provided paths are relative to <c>${ED}</c>, even if they begin with a slash.
</ti>
</tr>
</table>
next reply other threads:[~2023-04-29 15:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-29 15:29 Ulrich Müller [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
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-08-28 20:01 Göktürk Yüksek
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=1682781978.caa3e98b1431ceeead2924302bcc997d6214ba69.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