Bug#596286: apt.conf examples should include caching/proxy setup

[Clint Byrum <clint@ubuntu.com>]

On Sep 9, 2010, at 11:40 PM, Julian Andres Klode wrote:

> On Mi, 2010-09-08 at 11:52 -0700, Clint Byrum wrote:
>> Package: apt
>> Version: 0.8.3
>> Severity: wishlist
>> 
>> 
>> Forwarding this Ubuntu wishlist bug report:
>> 
>> https://bugs.launchpad.net/ubuntu/+source/apt/+bug/134201
>> 
>>> From Lars Noodén:
>> 
>> "Many sites have an HTTP+FTP proxy/cache already set up and running. If I
>> understand correctly would be possible to use Apt.conf to run requests
>> to Ubuntu's repositories through the proxy/cache. I would like the
>> examples document for apt.conf to include a sample configuration for
>> squid or some other common proxy/cache. (Note, this should not be
>> "apt-cacher", though it might be useful to mention "apt-cacher" in
>> *addition* to a regular proxy cache. However, since few sites have
>> apt-cacher in place, using an example of a regular proxy/cache is
>> needed.)
>> 
>> When setting up, updating, patching or upgrading a large site, speed
>> would be increased several orders of magnitude by having a local cache.
>> This would also be good for the Internet as it would reduce unnecessary
>> congestion."
>> 
>> I have confirmed that the examples in apt for 0.8.3 still do not contain
>> any examples for proxy setup.
>> 
> It is documented in apt.conf(5) and examples are
> in /usr/share/doc/apt/examples/configure-index.gz - what more do you
> want?
> 

Hi Julian,

I suppose I misspoke, I didn't mean there are not any examples, but
rather, that the examples I see do not satisfy the request.

I believe the original requester was asking for a short, clear
example of how and when to use a local proxy cache.

As an experienced apt user and long time sysadmin who has setup
many proxies, its really not clear even to me from those two examples
how to setup a simple connection to the proxy. I understand that
this is an example but without some context for each option its
really not clear what they do:

  // HTTP method configuration
  http 
  {
    Proxy "http://127.0.0.1:3128";;
    Proxy::http.us.debian.org "DIRECT";  // Specific per-host setting
    Timeout "120";
    Pipeline-Depth "5";
    AllowRedirect  "true";

...

I have also suggested to the original user that he submit a patch
to this bug report.