Bug#224509: [PROPOSAL] Correct spurious promise regarding TTY availability
* Wouter Verhelst
> That said, I don't think it's a good idea to do this. Many packages
> depend on having a controlling tty available, and aren't buggy since
> current policy allows it. Changing that would make all those packages
> instantly buggy, which should be avoided if at all possible (and it most
> certainly is possible)
These packages are already de facto buggy. I can't imagine that it
would matter to a user whether or no the failure resulted from a
spurious promise from policy or a slack maintainer -- the maintainer
script will fail, and that's all that matters.
There is however no doubt that this proposal will make a number of
packages instantly de jure buggy. That said, do note that it will
only be a "should" policy violation, so it will not justify any
bugs of release-critical severity.
Another thing worth noting is that the by far most popular method for
prompting users, debconf, already does the requred checking.
--
Tore Anderson
Reply to: