On Thu, Dec 28, 2006 at 03:48:38PM -0500, Jay Berkenbilt wrote: > 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.
You can rmdir the directory in the postinst (because it should be empty then) and then create the symlink manually. This is the most common solution I've found in existing packages and it looks reasonably sane and safe. > Do you know the motivation or history for this feature? My guess would be: The reason why dpkg doesn't replace symlinks with directories is probably to allow the local user/admin to relocate a directory tree and symlink it without breaking dpkg usage. The reason why dpkg doesn't replace directories with symlinks is probably because this would effectively require a rm -fr on the directory (or the creation of potentially very big backups) which is not a very good thing to do non-interactively. Gruesse, -- Frank Lichtenheld <[EMAIL PROTECTED]> www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
