1 |
Clarify the description for the dohard helper to indicate that both |
2 |
the created hardlink (as already noted on top of section) and its target |
3 |
are interpreted relatively to D. This is how the function is implemented |
4 |
in Paludis, PkgCore and Portage. |
5 |
|
6 |
There is no need to consider Prefix-relevant behavior since the helper |
7 |
is banned in all EAPIs supporting Prefix. |
8 |
--- |
9 |
pkg-mgr-commands.tex | 5 +++-- |
10 |
1 file changed, 3 insertions(+), 2 deletions(-) |
11 |
|
12 |
diff --git a/pkg-mgr-commands.tex b/pkg-mgr-commands.tex |
13 |
index 389d8c0..8405a2f 100644 |
14 |
--- a/pkg-mgr-commands.tex |
15 |
+++ b/pkg-mgr-commands.tex |
16 |
@@ -401,8 +401,9 @@ the current phase function has returned. |
17 |
\t{exeopts} call. |
18 |
Failure behaviour is EAPI dependent as per section~\ref{sec:failure-behaviour}. |
19 |
|
20 |
-\item[dohard] Takes two parameters. Creates a hardlink from the second to the first. In EAPIs |
21 |
- listed in table~\ref{tab:banned-commands-table}, this command is banned as per |
22 |
+\item[dohard] Takes two parameters. Creates a hardlink from the second to the first. Both paths are |
23 |
+ relative to the staging directory \t{D}. In EAPIs listed in |
24 |
+ table~\ref{tab:banned-commands-table}, this command is banned as per |
25 |
section~\ref{sec:banned-commands}. |
26 |
|
27 |
\item[doheader] \featurelabel{doheader} Installs the given header files into \t{/usr/include/}, |
28 |
-- |
29 |
2.12.2 |