> It's not a bug, it's a feature... > And documented in Policy, Section 6.6, point 4: > "A directory will never be replaced by a symbolic link to a directory or > vice versa; instead, the existing state (symlink or not) will be left > alone and dpkg will follow the symlink if there is one."
I checked the dpkg documentation. I vaguely remembered having seen this before. I guess it's been a while since I've read the policy in detail. In any case, the fact that it's documented doesn't make it right. I think empty directories should be allowed to be replaced. Otherwise, how do you handle situations such as the one I described? Right now, people upgrading from sarge to etch will end up with several empty directories in /usr/share/doc. Do you know the motivation or history for this feature? -- Jay Berkenbilt <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
