sources.list.5.xml 9.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218
  1. <?xml version="1.0" encoding="utf-8" standalone="no"?>
  2. <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
  3. "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
  4. <!ENTITY % aptent SYSTEM "apt.ent">
  5. %aptent;
  6. ]>
  7. <refentry>
  8. <refentryinfo>
  9. &apt-author.jgunthorpe;
  10. &apt-author.team;
  11. &apt-email;
  12. &apt-product;
  13. <!-- The last update date -->
  14. <date>29 February 2004</date>
  15. </refentryinfo>
  16. <refmeta>
  17. <refentrytitle>sources.list</refentrytitle>
  18. <manvolnum>5</manvolnum>
  19. </refmeta>
  20. <!-- Man page title -->
  21. <refnamediv>
  22. <refname>sources.list</refname>
  23. <refpurpose>Package resource list for APT</refpurpose>
  24. </refnamediv>
  25. <refsect1><title>Description</title>
  26. <para>The package resource list is used to locate archives of the package
  27. distribution system in use on the system. At this time, this manual page
  28. documents only the packaging system used by the Debian GNU/Linux system.
  29. This control file is located in <filename>/etc/apt/sources.list</filename></para>
  30. <para>The source list is designed to support any number of active sources and a
  31. variety of source media. The file lists one source per line, with the
  32. most preferred source listed first. The format of each line is:
  33. <literal>type uri args</literal> The first item, <literal>type</literal>
  34. determines the format for <literal>args</literal> <literal>uri</literal> is
  35. a Universal Resource Identifier
  36. (URI), which is a superset of the more specific and well-known Universal
  37. Resource Locator, or URL. The rest of the line can be marked as a comment
  38. by using a #.</para>
  39. </refsect1>
  40. <refsect1><title>The deb and deb-src types</title>
  41. <para>The <literal>deb</literal> type describes a typical two-level Debian
  42. archive, <filename>distribution/component</filename>. Typically,
  43. <literal>distribution</literal> is generally one of
  44. <literal>stable</literal> <literal>unstable</literal> or
  45. <literal>testing</literal> while component is one of <literal>main</literal>
  46. <literal>contrib</literal> <literal>non-free</literal> or
  47. <literal>non-us</literal> The
  48. <literal>deb-src</literal> type describes a debian distribution's source
  49. code in the same form as the <literal>deb</literal> type.
  50. A <literal>deb-src</literal> line is required to fetch source indexes.</para>
  51. <para>The format for a <filename>sources.list</filename> entry using the
  52. <literal>deb</literal> and <literal>deb-src</literal> types are:</para>
  53. <literallayout>deb uri distribution [component1] [component2] [...]</literallayout>
  54. <para>The URI for the <literal>deb</literal> type must specify the base of the
  55. Debian distribution, from which APT will find the information it needs.
  56. <literal>distribution</literal> can specify an exact path, in which case the
  57. components must be omitted and <literal>distribution</literal> must end with
  58. a slash (/). This is useful for when only a particular sub-section of the
  59. archive denoted by the URI is of interest.
  60. If <literal>distribution</literal> does not specify an exact path, at least
  61. one <literal>component</literal> must be present.</para>
  62. <para><literal>distribution</literal> may also contain a variable,
  63. <literal>$(ARCH)</literal>
  64. which expands to the Debian architecture (i386, m68k, powerpc, ...)
  65. used on the system. This permits architecture-independent
  66. <filename>sources.list</filename> files to be used. In general this is only
  67. of interest when specifying an exact path, <literal>APT</literal> will
  68. automatically generate a URI with the current architecture otherwise.</para>
  69. <para>Since only one distribution can be specified per line it may be necessary
  70. to have multiple lines for the same URI, if a subset of all available
  71. distributions or components at that location is desired.
  72. APT will sort the URI list after it has generated a complete set
  73. internally, and will collapse multiple references to the same Internet
  74. host, for instance, into a single connection, so that it does not
  75. inefficiently establish an FTP connection, close it, do something else,
  76. and then re-establish a connection to that same host. This feature is
  77. useful for accessing busy FTP sites with limits on the number of
  78. simultaneous anonymous users. APT also parallelizes connections to
  79. different hosts to more effectively deal with sites with low bandwidth.</para>
  80. <para>It is important to list sources in order of preference, with the most
  81. preferred source listed first. Typically this will result in sorting
  82. by speed from fastest to slowest (CD-ROM followed by hosts on a local
  83. network, followed by distant Internet hosts, for example).</para>
  84. <para>Some examples:</para>
  85. <literallayout>
  86. deb http://http.us.debian.org/debian stable main contrib non-free
  87. deb http://http.us.debian.org/debian dists/stable-updates/
  88. </literallayout>
  89. </refsect1>
  90. <refsect1><title>URI specification</title>
  91. <para>The currently recognized URI types are cdrom, file, http, and ftp.
  92. <variablelist>
  93. <varlistentry><term>file</term>
  94. <listitem><para>
  95. The file scheme allows an arbitrary directory in the file system to be
  96. considered an archive. This is useful for NFS mounts and local mirrors or
  97. archives.</para></listitem>
  98. </varlistentry>
  99. <varlistentry><term>cdrom</term>
  100. <listitem><para>
  101. The cdrom scheme allows APT to use a local CDROM drive with media
  102. swapping. Use the &apt-cdrom; program to create cdrom entries in the
  103. source list.</para></listitem>
  104. </varlistentry>
  105. <varlistentry><term>http</term>
  106. <listitem><para>
  107. The http scheme specifies an HTTP server for the archive. If an environment
  108. variable <envar>http_proxy</envar> is set with the format
  109. http://server:port/, the proxy server specified in
  110. <envar>http_proxy</envar> will be used. Users of authenticated
  111. HTTP/1.1 proxies may use a string of the format
  112. http://user:pass@server:port/
  113. Note that this is an insecure method of authentication.</para></listitem>
  114. </varlistentry>
  115. <varlistentry><term>ftp</term>
  116. <listitem><para>
  117. The ftp scheme specifies an FTP server for the archive. APT's FTP behavior
  118. is highly configurable; for more information see the
  119. &apt-conf; manual page. Please note that a ftp proxy can be specified
  120. by using the <envar>ftp_proxy</envar> environment variable. It is possible
  121. to specify a http proxy (http proxy servers often understand ftp urls)
  122. using this method and ONLY this method. ftp proxies using http specified in
  123. the configuration file will be ignored.</para></listitem>
  124. </varlistentry>
  125. <varlistentry><term>copy</term>
  126. <listitem><para>
  127. The copy scheme is identical to the file scheme except that packages are
  128. copied into the cache directory instead of used directly at their location.
  129. This is useful for people using a zip disk to copy files around with APT.</para></listitem>
  130. </varlistentry>
  131. <varlistentry><term>rsh</term><term>ssh</term>
  132. <listitem><para>
  133. The rsh/ssh method invokes rsh/ssh to connect to a remote host
  134. as a given user and access the files. No password authentication is
  135. possible, prior arrangements with RSA keys or rhosts must have been made.
  136. Access to files on the remote uses standard <command>find</command> and
  137. <command>dd</command>
  138. commands to perform the file transfers from the remote.</para></listitem>
  139. </varlistentry>
  140. </variablelist>
  141. </para>
  142. </refsect1>
  143. <refsect1><title>Examples</title>
  144. <para>Uses the archive stored locally (or NFS mounted) at /home/jason/debian
  145. for stable/main, stable/contrib, and stable/non-free.</para>
  146. <literallayout>deb file:/home/jason/debian stable main contrib non-free</literallayout>
  147. <para>As above, except this uses the unstable (development) distribution.</para>
  148. <literallayout>deb file:/home/jason/debian unstable main contrib non-free</literallayout>
  149. <para>Source line for the above</para>
  150. <literallayout>deb-src file:/home/jason/debian unstable main contrib non-free</literallayout>
  151. <para>Uses HTTP to access the archive at archive.debian.org, and uses only
  152. the hamm/main area.</para>
  153. <literallayout>deb http://archive.debian.org/debian-archive hamm main</literallayout>
  154. <para>Uses FTP to access the archive at ftp.debian.org, under the debian
  155. directory, and uses only the stable/contrib area.</para>
  156. <literallayout>deb ftp://ftp.debian.org/debian stable contrib</literallayout>
  157. <para>Uses FTP to access the archive at ftp.debian.org, under the debian
  158. directory, and uses only the unstable/contrib area. If this line appears as
  159. well as the one in the previous example in <filename>sources.list</filename>.
  160. a single FTP session will be used for both resource lines.</para>
  161. <literallayout>deb ftp://ftp.debian.org/debian unstable contrib</literallayout>
  162. <para>Uses HTTP to access the archive at nonus.debian.org, under the
  163. debian-non-US directory.</para>
  164. <literallayout>deb http://nonus.debian.org/debian-non-US stable/non-US main contrib non-free</literallayout>
  165. <para>Uses HTTP to access the archive at nonus.debian.org, under the
  166. debian-non-US directory, and uses only files found under
  167. <filename>unstable/binary-i3866</filename> on i386 machines,
  168. <filename>unstable/binary-m68k</filename> on m68k, and so
  169. forth for other supported architectures. [Note this example only
  170. illustrates how to use the substitution variable; non-us is no longer
  171. structured like this]
  172. <literallayout>deb http://ftp.de.debian.org/debian-non-US unstable/binary-$(ARCH)/</literallayout>
  173. </para>
  174. </refsect1>
  175. <refsect1><title>See Also</title>
  176. <para>&apt-cache; &apt-conf;
  177. </para>
  178. </refsect1>
  179. &manbugs;
  180. </refentry>