Bug#333921: priority of mouse template too low

[Robert Millan <rmh@aybabtu.com>]

On Mon, Oct 17, 2005 at 04:54:02PM +1000, Daniel Stone wrote:
> On Mon, Oct 17, 2005 at 08:47:15AM +0200, Robert Millan wrote:
> > On Sat, Oct 15, 2005 at 02:21:15AM +1000, Daniel Stone wrote:
> > > I don't think this template should be high unless the mouse cannot be
> > > detected.  On Linux/(i386|amd64|powerpc), which, last I heard, amounted
> > > to well over 95% of Debian archive downloads, /dev/input/mice will
> > > basically always work just fine.  So there's no reason to always prompt
> > > if you don't need to; it's insane.
> > 
> > What happens when auto-detection is not performed (either declined by user, or
> > because mdetect is not installed)?
> 
> 'unless the mouse cannot be detected'.
> 
> try to run mdetect
> if this works:
>   prompt with priority low
> else:
>   prompt with priority high

I'm not sure why, but on a system where mdetect is not installed,
"dpkg-reconfigure -phigh" doesn't trigger any mouse-related questions.

Same happens if I put a copy of /bin/false into /usr/bin/mdetect, forcing it to
fail.

-- 
Robert Millan