File: control

package info (click to toggle)
auto-apt-proxy 17
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 192 kB
  • sloc: sh: 428; makefile: 11
file content (51 lines) | stat: -rw-r--r-- 2,054 bytes parent folder | download
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
45
46
47
48
49
50
51
Source: auto-apt-proxy
Section: net
Priority: optional
Maintainer: Antonio Terceiro <terceiro@debian.org>
Build-Depends: debhelper (>= 11~),
               dh-sequence-shell-completions,
               dpkg-dev (>= 1.17.14~),
               shellcheck <!nocheck>,
               pandoc,
Standards-Version: 4.7.0
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: busybox | iproute2,
Depends: apt,
         ${misc:Depends},
         ${shlibs:Depends},
Suggests: avahi-utils,
Description: automatic detector of common APT proxy settings
 auto-apt-proxy installs itself as an APT proxy autodetector, and detects
 common setups by checking some hosts on the local network 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 at least these cases:
 .
   * 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.
   * Systems where the `apt-proxy` hostname resolves to a valid IP address
     and a supported proxy is detected at that address.
 .
 The following APT proxy servers are supported and automatically detected:
   * apt-cacher-ng
   * approx
   * apt-cacher
   * squid-deb-proxy
   * any proxy advertised by an _apt_proxy._tcp SRV record in your domain
   * any proxy advertised by an _apt_proxy._tcp SRV record in mDNS (needs
     avahi-tools to be installed, and avahi-daemon to be installed and
     running)
 .
 This package has a minimal set of dependencies in order to minimize the
 influence on systems where it is installed. However, if neither iproute2 nor
 busybox are installed, functionality is severily limited.