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/ED. This is how the function is |
4 |
implemented in Paludis, PkgCore and Portage. |
5 |
--- |
6 |
pkg-mgr-commands.tex | 6 ++++-- |
7 |
1 file changed, 4 insertions(+), 2 deletions(-) |
8 |
|
9 |
diff --git a/pkg-mgr-commands.tex b/pkg-mgr-commands.tex |
10 |
index 389d8c0..4bed690 100644 |
11 |
--- a/pkg-mgr-commands.tex |
12 |
+++ b/pkg-mgr-commands.tex |
13 |
@@ -401,8 +401,10 @@ the current phase function has returned. |
14 |
\t{exeopts} call. |
15 |
Failure behaviour is EAPI dependent as per section~\ref{sec:failure-behaviour}. |
16 |
|
17 |
-\item[dohard] Takes two parameters. Creates a hardlink from the second to the first. In EAPIs |
18 |
- listed in table~\ref{tab:banned-commands-table}, this command is banned as per |
19 |
+\item[dohard] Takes two parameters. Creates a hardlink from the second to the first. Both paths are |
20 |
+ relative to the staging directory including the offset-prefix \t{ED} in offset-prefix aware EAPIs, |
21 |
+ or just the staging directory \t{D} in offset-prefix agnostic EAPIs. In EAPIs listed in |
22 |
+ table~\ref{tab:banned-commands-table}, this command is banned as per |
23 |
section~\ref{sec:banned-commands}. |
24 |
|
25 |
\item[doheader] \featurelabel{doheader} Installs the given header files into \t{/usr/include/}, |
26 |
-- |
27 |
2.12.2 |