Re: a bit policy, a bit devel [was: Re: Find the display]
> Thats stuff that can actually cost money and if it does you will hate
> the stupid sawfish *sorry, but thats a _absolutly random_ :) name,
> nothing against sawfish, change at will* for bothering you to drive to
> the system and press return.
Debconf should be able to handle things like that with the 'web' option.
If you are remotely installing, you shouldn't depend on an ssh or telnet
session staying up. And vice versa, upgrading a webserver should NOT let
you use the 'web' option of debconf.
yes, I agree, having to go to the machine in question is a _bad_ thing,
and any installation that can 'blow up' like that, SHOULD warn you at a
minimum, and prevent you from doing it as a maximum. (ssh should look for
running ssh processes and refuse to upgrade, for instance, if you are
currently using it, unless you specifically force it to when asked)
This is up to the maintainer to keep in mind, and it should be filed as
a bugreport against the package if someone finds a problem like that with
an install.
Seth
Reply to: