1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
|
Source: auto-apt-proxy
Section: net
Priority: optional
Maintainer: Antonio Terceiro <terceiro@debian.org>
Build-Depends: debhelper (>= 11~),
dpkg-dev (>= 1.17.14~),
shellcheck <!nocheck>,
Standards-Version: 4.2.1
Homepage: https://salsa.debian.org/debian/auto-apt-proxy
Vcs-Git: https://salsa.debian.org/debian/auto-apt-proxy.git
Vcs-Browser: https://salsa.debian.org/debian/auto-apt-proxy
Rules-Requires-Root: no
Package: auto-apt-proxy
Architecture: all
Recommends: iproute2,
Depends: apt,
${misc:Depends},
${shlibs:Depends},
Description: automatic detector of common APT proxy settings
auto-apt-proxy installs itself as an APT proxy autodetector, and detects
common setups by checking localhost and the network default gateway for
well-known APT proxies such as apt-cacher-ng.
.
This package is most useful for development environments, and will Do The
Right Thing for:
.
* build chroots, with a proxy running on the host system.
* docker/lxc containers, with a proxy running on the host system.
* Virtual machines with NAT networking, with a proxy running on the host
* system.
* any other system, with a proxy running on its default gateway.
.
The following APT proxy servers are supported and automatically detected:
* apt-cacher-ng
* approx
* apt-cacher
.
This package has a minimal set of dependencies in order to minimize the
influence on systems where it is installed.
.
For corporate desktop/server deployments, where the APT proxy can be located
at any arbitrary host, you should probably try the `squid-deb-proxy-client`
package instead.
|
