summaryrefslogtreecommitdiff
path: root/fi/using-d-i/modules/apt-setup.xml
blob: 4f9d7d465f4cb4b8b7236b9d81b6ef3ccbd2b4c0 (plain)
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
<!-- retain these comments for translator revision tracking -->
<!-- original version: 33814 untranslated -->

   <sect3 id="apt-setup">
   <title>Configuring apt</title>

<para>

The main means that people use to install packages on their system is
via a program called <command>apt-get</command>, from the
<classname>apt</classname> package.<footnote>

<para>

Note that the actual program that installs packages is called
<command>dpkg</command>.  However, this program is more of a low-level
tool.  <command>apt-get</command> is a higher-level tool as it will
invoke <command>dpkg</command> as appropriate and also because it knows
to install other packages which are required for the package you're
trying to install, as well as how to retrieve the package from your
CD, the network, or wherever.

</para>
</footnote>
Other front-ends for package management, like <command>aptitude</command>
and <command>synaptic</command> are also in use and depend on
<command>apt-get</command>. These front-ends are recommended for new users,
since they integrate some additional features (package searching and status checks)
in a nice user interface.

</para><para>

<command>apt</command> must be configured so that it knows where to retrieve
packages from. The installer largely takes care of this automatically based on
what it knows about your installation medium. The results of this configuration
are written to the file /etc/apt/sources.list, and you can examine and edit
it to your liking after the install is complete.

</para>

   </sect3>