The issue is not fixed by simply quoting policy and taking no action to correct the problem.
10.5 specifies that "In general, symbolic links within a top-level directory should be relative".
It should be fairly easy to make a symlink that does work on the target system if it takes into account the actual location of the dir/file. Granted, that will make the symlink have to be dynamically created at installation, but that will neither break policy nor create broken links.
In addition, the "in general" and "should" both suggest that 10.5 is a general guideline, and does not preclude exceptions if the result would otherwise be a broken package installation, as it is in this case.
Evan On Sun, 20 Jun 2010, Debian Bug Tracking System wrote:
This is an automatic notification regarding your Bug report which was filed against the linux-headers-2.6.32-5-common package: #586491: Broken symlinks created for package if /usr/src is a symlink It has been closed by Bastian Blank <wa...@debian.org>. Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Bastian Blank <wa...@debian.org> by replying to this email. -- 586491: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586491 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
-- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
