dpkg bug?
The new recode 3.5 now contains a library, so following policy about
shared libraries I have splitted the main package in three: recode,
librecode0 and librecode-dev.
However, I had the "bright" idea of taking advantage of the fact that
recode depends on librecode0 by making /usr/doc/recode to be a symlink
to /usr/doc/librecode0.
Well, dpkg does not handle this. When upgrading from recode 3.4.1,
/usr/doc/recode becomes an empty directory, not a symlink.
Questions:
*) Is this a dpkg bug?
*) Regardless of it being a bug or not: It is documented that probably it
should not be done?
Thanks.
--
"e09bcceedb9383481fd22968419e0833" (a truly random sig)
Reply to: