When to run update-alternatives --remove?
recently, I have experienced two cases where a package
resetted alternative, which I had setted manually, to
auto mode when I upgraded it.
For example, gs did run update-alternatives as follows
in its prerm:
if [ -x /usr/sbin/update-alternatives ]; then
update-alternatives --remove gs \
that is, "update-alternatives --remove" was called even at
I'm not sure but it seems natural not to call
"update-alternatives --remove" at upgrade.
Or is there any good reason to run "update-alternatives --remove"
at upgrade ?
One moe package which does the same thing is tetex-bin
which I am one of the maintainers ;) I would like to
know I should fix this behavior or not in tetex-bin ...
Best regards, 2002/10/3
Debian Developer & Debian JP Developer - much more I18N of Debian
Atsuhito Kohda <firstname.lastname@example.org>
Department of Math., Univ. of Tokushima