Bug#261415: network installation always asks for proxy

[Geert Stappers <stappers@debian.org>]

> 
> Of course, incomprehensible questions will also drive users elsewhere,
> so we need to make sure that people understand that they almost
> certainly don't care, unless they already know that they do care.

This e-mail is about "worry about a proxy
   when there is need to worry about a proxy"

> I could imagine using auto-detection to populate default values for a
> site's proxy, assuming that the software to achieve that has a decent
> chance of success, and isn't too big.
> 
> Alternatively, one could make sure that the subsequent package download
> progress page made it clear that it would be safe to cancel that, and
> that doing so would let one back up and specify a proxy to go via and
> then retry the install -- that would let the person looking at a
> download that's going depressingly slowly plenty of time to remember
> that they have a faster alternative, and the reassurance that they can
> switch to it without having to start the install from scratch (assuming
> we can get the code to work that way).

Currently we have these steps

* hardware detect
* network configuration with DHCP and manual config upon fail
* allways ask for proxy
* do the download

What I would like to see, are these steps

* hardware detect
* network configuration with DHCP and manual configuration upon failure
* inform user there is test download going on, allow "quick fail" (don't wait for time out)
** upon fail: ask for a proxy configuration 
** upon succes: fine, just continue
* do the download



Groeten
Geert Stappers
-- 
Leven en laten leven