Saurik's version of apt managed for tvOS/ARM64
Julian Andres Klode
374a6efa1d
travis: Move codecov from after_success to after_script
|
10 年 前 | |
|---|---|---|
| CMake | 10 年 前 | |
| abicheck | 10 年 前 | |
| apt-inst | 10 年 前 | |
| apt-pkg | 10 年 前 | |
| apt-private | 10 年 前 | |
| cmdline | 10 年 前 | |
| completions | 10 年 前 | |
| debian | 10 年 前 | |
| doc | 10 年 前 | |
| dselect | 10 年 前 | |
| ftparchive | 10 年 前 | |
| methods | 10 年 前 | |
| po | 10 年 前 | |
| test | 10 年 前 | |
| vendor | 10 年 前 | |
| .gitignore | 10 年 前 | |
| .travis.yml | 10 年 前 | |
| AUTHORS | 10 年 前 | |
| CMakeLists.txt | 10 年 前 | |
| COPYING | 10 年 前 | |
| COPYING.GPL | 22 年 前 | |
| README.SrvRecords | 10 年 前 | |
| README.md | 10 年 前 | |
| README.progress-reporting | 11 年 前 | |
| mirror-failure.py | 19 年 前 | |
| prepare-release | 10 年 前 | |
| shippable.yml | 10 年 前 |
README.SrvRecords
DNS SRV record support in apt
=============================
Apt supports a subset of the DNS SRV server records protocol as
described in RFC 2782 for service discovery.
Before connecting to the requested server APT will send a SRV
record request of the form "_$protocol._tcp._$host", e.g.
"_http._tcp.ftp.debian.org" or "_http._tcp.security.debian.org".
If the server sends SRV records
as a reply APT will use those to connect to the server(s) in
this reply. It will honor the "priority" field in the reply.
However it does not implement the "weight" algorithm as described
in RFC 2782. It will use an equal weight for each server of the
same priority.
If connecting to a server fails APT will retry with the next one
and remove the server from the list of valid servers for this
session.
=============================
Apt supports a subset of the DNS SRV server records protocol as
described in RFC 2782 for service discovery.
Before connecting to the requested server APT will send a SRV
record request of the form "_$protocol._tcp._$host", e.g.
"_http._tcp.ftp.debian.org" or "_http._tcp.security.debian.org".
If the server sends SRV records
as a reply APT will use those to connect to the server(s) in
this reply. It will honor the "priority" field in the reply.
However it does not implement the "weight" algorithm as described
in RFC 2782. It will use an equal weight for each server of the
same priority.
If connecting to a server fails APT will retry with the next one
and remove the server from the list of valid servers for this
session.