[debhelper-devel] Bug#860091: Bug#860091: Bug#860091: debhelper: Please be more verbose in the dh_link man page
niels at thykier.net
Wed Apr 12 09:08:00 UTC 2017
> Quoting Niels Thykier (2017-04-12 10:46:00)
>> One question though, are you sure about the path not being allowed to have a
>> leading slash? AFAICT, the code at least handles the link target perfectly
>> fine if it has a leading slash. And I am inclined to say that it is a bug if
>> it does not support leading slashes in the link name either.
> no I'm not sure about that and I didn't look into the code. I just inspected a
> random sample of *.links files I found on codesearch.d.n.
> My confusion here was, that the man page is talking about absolute paths but
> those start with a leading slash. If the code allows both, then that should be
> mentioned or otherwise people reading existing *.links files will be confused.
> cheers, josch
Thanks, I have added that clarification:
diff --git a/dh_link b/dh_link
index 815c81db..ac67109a 100755
@@ -27,9 +27,9 @@ are the symlinks that will be created (called B<link
L<ln(1)>). There B<must> be an equal number of source and destination
-Be sure you B<do> specify the absolute path (without leading slash) to
-both the source and destination files (unlike you would do if you were
-using something like L<ln(1)>).
+Be sure you B<do> specify the absolute path to both the source and
+destination files (unlike you would do if you were using something
+like L<ln(1)>). Please note that the leading slash is optional.
B<dh_link> will generate symlinks that comply with Debian policy - absolute
when policy says they should be absolute, and relative links with as short
@@ -57,7 +57,7 @@ L<ln(1)>). Thus the pairs of source and destination
files in each line
are give in the same order as they would be given to L<ln(1)>.
In contrast to L<ln(1)>, source and destination paths must be absolute
-without a leading slash.
+(the leading slash is optional).
More information about the debhelper-devel