(Closes: #627490)
* Fix the example of creating a /usr/local subdirectory to not fail if
the chown or chmod fail. Thanks, Joey Hess. (Closes: #617315)
+ * Clarify the requirements for symlinks from inside one top-level
+ directory to another and add examples and a rationale. Thanks,
+ Carsten Hey. (Closes: #626338)
* Add the release date of 3.9.2.0 to upgrading-checklist.
* Fix ordering of the last entries in the 3.9.2.0 upgrading-checklist.
* Fix typo in upgrading-checklist entry for multiarch paths. Thanks,
<heading>Symbolic links</heading>
<p>
- In general, symbolic links within a top-level directory
- should be relative, and symbolic links pointing from one
- top-level directory into another should be absolute. (A
- top-level directory is a sub-directory of the root
- directory <file>/</file>.)
+ In general, symbolic links within a top-level directory should
+ be relative, and symbolic links pointing from one top-level
+ directory to or into another should be absolute. (A top-level
+ directory is a sub-directory of the root
+ directory <file>/</file>.) For example, a symbolic link
+ from <file>/usr/lib/foo</file> to <file>/usr/share/bar</file>
+ should be relative (<file>../bar</file>), but a symbolic link
+ from <file>/var/run</file> to <file>/run</file> should be
+ absolute.<footnote>
+ This is necessary to allow top-level directories to be
+ symlinks. If linking <file>/var/run</file>
+ to <file>/run</file> were done with the relative symbolic
+ link <file>../run</file>, but <file>/var</file> were a
+ symbolic link to <file>/srv/disk1</file>, the symbolic link
+ would point to <file>/srv/run</file> rather than the intended
+ target.
+ </footnote>
</p>
<p>