Package: apt-proxy Version: 1.9.32 Severity: wishlist I would suggest, that apt-proxy should support virtual servers by interpreting the "Host: ...." line of the http-request as the address for the virtual servers. This has the following advantages: - The download process is parallelizable. - Because most of the package utilities don't show the complete path one doesn't know from which server the package *really* comes.
Example: Server apt-proxy.localnet, backend "debian", then the following "sources.list"-entries should have the same effect: deb http://apt-proxy.localnet:9999/debian testing main non-free contrib deb http://debian.apt-proxy.localnet:9999 testing main non-free contrib Best whishes and thanks for the good work! Jan -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-k7 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages apt-proxy depends on: ii adduser 3.79 Add and remove users and groups ii bzip2 1.0.2-10 high-quality block-sorting file co ii debconf [debconf-2.0] 1.4.59 Debian configuration management sy ii logrotate 3.7.1-2 Log rotation utility ii python 2.3.5-3 An interactive high-level object-o ii python-apt 0.6.13.1 Python interface to libapt-pkg ii python-bsddb3 3.3.0-6 Python interface to libdb3 ii python-twisted 2.0.1-5 Event-based framework for internet ii python2.3 2.3.5-8 An interactive high-level object-o apt-proxy recommends no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
