Buchan Milne wrote: > On Sat, 2 Aug 2003, David Walser wrote: > >> Ok, we're both wrong. It's not curl or rpmdrake's job >> to check for this, it's urpmi's. >> >> Imagine this scenario, you've got a proxy configured, >> which is also the location of one of your urpmi >> sources, but you have sources from other servers too. >> You run a urpmi command to install some packages, some >> which will come from each place. If you don't do >> http_proxy="" first, the ones from that server won't >> work, but if you do, the ones from the other servers >> won't use the proxy. >> >> So if urpmi is installing something from the same host >> as the proxy, it shouldn't use the proxy for that package. > > Or, maybe urpmi should have a per-source flag on whether to use a proxy or > not (we assume the proxy is the same for all sources using a proxy). Why? > Well, it's not only the proxy host that you may not want to contact via > the proxy, it may include hosts on the same side of the proxy as you. > > In the end, the problem is that there is no global equivalent of a proxy > exclude list (although I see no reason why there shouldn't be). Of course, > there are a few other things that would be nice to have per-source > configuration for (my vote would be per-source gpg signatures), and it > would be nice if they were all accessible from the source^H^H^H^H^H^Hmedia > configuration tool.
Oh thanks for reminding me Buchan, there is another thing that would be nice to be configurable per source: Bandwidth limit. So you can limit how much bandwidth it taken by urpmi downloading things (hdlists, packages, etc) rsync and wget both support options for this, and I imagine curl does too, so we could offer a bwlimit for just about any kind of source.
