[ zurück ] [ Inhalt ] [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ] [ 6 ] [ 7 ] [ 8 ] [ 9 ] [ 10 ] [ 11 ] [ 12 ] [ 13 ] [ 14 ] [ weiter ]


APT HOWTO
Kapitel 2 - Einführung


Am Anfang war das .tar.gz. Benutzer mußten jedes Programm, welches sie auf ihren GNU/Linux-Systemen benutzen wollten, selbst kompilieren. Zu Beginn der Entwicklung des Debian-Projekts erachtete man es für notwendig, daß das System eine Methode zum Verwalten der Pakete, die auf dem System installiert sind, enthält. Man gab dieser Methode den Namen dpkg. Dadurch war das erste 'Paket' auf GNU/Linux geboren, bevor Red Hat sich entschied, ihr eigenes RPM-System zu erschaffen.

Schnell standen die Macher von GNU/Linux vor einem neuen Problem. Sie brauchten ein schnelles, praktisches und effizientes Mittel, um Pakete zu installieren, das Abhängigkeiten automatisch behandeln und ihre Konfigurationsdateien während des Aktualisierens berücksichtigen würde. Und wieder war es das Debian-Projekt, das den Weg machte und APT, das "Advanced Packaging Tool", welches seitdem von Connectiva auf RPM portiert und von einigen anderen Distributionen übernommen wurde, das Licht der Welt erblicken ließ.

Diese Anleitung versucht nicht, apt-rpm (den Connectiva-Port von APT) zu behandeln, aber Patches für dieses Dokument, welche es tun, sind willkommen.

Diese Dokumentation basiert auf der nächsten Debian-Version: Sarge.


2.1 Basic terminology and concepts

Here you can find some basic terminology and concepts used on this manual:

APT source: an APT source is a location (often on the internet, or possibly on a CDROM or other location) which functions as a repository of Debian packages, see Die Datei /etc/apt/sources.list, Abschnitt 4.1.

APT source line: an APT source line is a line you add to a configuration file to tell APT about the "Apt sources" you want to use, see Die Datei /etc/apt/sources.list, Abschnitt 4.1.

binary package: a binary package is a .deb file prepared to be installed by the package manager (dpkg), it may include binary files but may also carry just architecture-independent data -- it's called binary package either way.

debian-native: package created specifically for Debian, this kind of package usually has the debian control files inside the original source and every new version of the package is also a new version of the original program or data.

debianize: verb usually used to mean "prepare for use with Debian" or, more simply put, packaged in .deb format.

source package: a source package is really an abstract definition to a set of two or three files which are part of the deb source format: a .dsc file, which contains information about the package, also called source control file; a .orig.tar.gz file, which contains the original upstream source for that package -- you may also find this being called .tar.gz, simply, with no .orig, meaning this is a debian-native package; a .diff.gz file, which carries the modifications made to the original source to "debianize" the package -- you will not find this kind of file on a debian-native package.

upstream: this word usually means something that comes from the original developer of the software or data, or the developer himself.

virtual packages: virtual packages are packages that do not really exist, but that are generic services "provided" by some specific packages -- the most common example is the mail-transport-agent package, to which packages that need an MTA[1] can specify a dependency while keeping the user choice as to which MTA to use.


[ zurück ] [ Inhalt ] [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ] [ 6 ] [ 7 ] [ 8 ] [ 9 ] [ 10 ] [ 11 ] [ 12 ] [ 13 ] [ 14 ] [ weiter ]


APT HOWTO

2.0.2 - October 2006

Gustavo Noronha Silva kov@debian.org
Deutsche Übersetzung: David Spreen netzwurm@debian.org