Annotated edit history of
PackageManagementTool version 27, including all changes.
View license author blame.
| Rev |
Author |
# |
Line |
| 26 |
PeterHewett |
1 |
Most PackageManagementTool~s revolve around binary distributions of [Packages | Package]. That is, they consult a repository of pre-compiled packages and install the package best suited to your system architecture. They may also offer source packages, allowing you to build the [Package] locally with whatever patches and optimization or configuration options you may have chosen. Other PackageManagementTool~s are source based - they may not even provide binary [Package]s at all, but at least try really hard to avoid them. These download the sources for a [Package], apply any vendor-provided patches, then compile on the local machine. This process takes considerably longer, but some people swear it gives them much better performance. It does have the advantage that you can tailor the system very closely to your desires, but is not much fun on slow machines, particularly for the desktop where such mammoths as [GNOME], [KDE], [Mozilla], and [OpenOffice] are waiting to occupy your machine for hours on end. |
| 18 |
AristotlePagaltzis |
2 |
|
| 16 |
AristotlePagaltzis |
3 |
There are several main 'flavours' of PackageManagementTool in use in various LinuxDistribution. These include: |
| 10 |
AristotlePagaltzis |
4 |
|
| 22 |
AristotlePagaltzis |
5 |
<tt>rpm</tt>: |
| 27 |
AristotlePagaltzis |
6 |
RedHat [Package] Manager, used not only by RedHat but also a number of others. Its [RPM] format for [Package]s has become a sort of standard because it was the first one used in any LinuxDistribution that had any form of dependency management. |
| 22 |
AristotlePagaltzis |
7 |
<tt>dpkg</tt>: |
| |
|
8 |
This is [Debian]'s [Package] manager. KnoppixLinux, [Progeny] and other LinuxDistribution~s are "Debian-based" and thus use this as well. FileFormat is [Deb]. |
| |
|
9 |
<tt>.tgz</tt>: |
| |
|
10 |
[Slackware] uses nearly plain TarBall~s that include a description and a postinstall script. |
| |
|
11 |
<tt>ports</tt>: |
| |
|
12 |
This is the source based PackageManagementTool that [BSD] uses. Several LinuxDistribution~s use a similar idea. |
| |
|
13 |
<tt>portage</tt>: |
| |
|
14 |
[Gentoo]'s version of source based PackageManagement, driven by a tool called <tt>emerge</tt>. |
| |
|
15 |
<tt>spell</tt>: |
| |
|
16 |
Sorceror Linux has a 'spell book' approach to source based PackageManagement. |
| 10 |
AristotlePagaltzis |
17 |
|
| |
|
18 |
Frontends to these tools include: |
| |
|
19 |
|
| 23 |
AristotlePagaltzis |
20 |
__Up2date__: |
| 25 |
AristotlePagaltzis |
21 |
A front-end to rpm provided by RedHat for RedHat and FedoraCore. You get to use it on one machine per user free, and can pay for the right to use it on more machines. |
| |
|
22 |
[Yum]: |
| |
|
23 |
FedoraCore's conconction. The vendor-recommended way to install software on that distribution. |
| 23 |
AristotlePagaltzis |
24 |
[APT]: |
| 25 |
AristotlePagaltzis |
25 |
One of the best tools around. It traditionally wraps <tt>dpkg</tt>, but there is an AptForRpm variant now (and rapidly gaining popularity). It was the first front-end to nicely handle dependencies: <tt>apt-get install foo</tt> will automatically download and install not only <tt>foo</tt>, but also any unfulfilled dependencies <tt>foo</tt> may have. There are lots of supplemental utilities surrounding -- see DebianPackageTools. |
| 26 |
PeterHewett |
26 |
[urpmi]: |
| 27 |
AristotlePagaltzis |
27 |
[Mandriva]'s PackageManagementTool based on [RPM]. |
