Differences between version 21 and revision by previous author of PackageManagementTool.
Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History
Newer page: | version 21 | Last edited on Monday, February 2, 2004 7:30:17 pm | by PhilNewcombe | Revert |
Older page: | version 20 | Last edited on Monday, February 2, 2004 3:27:28 pm | by AristotlePagaltzis | Revert |
@@ -1,5 +1,5 @@
-Most [PackageManagementTool]s revolve around binary distributions of [Package]s. 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 taylor
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.
+Most [PackageManagementTool]s revolve around binary distributions of [Package]s. 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.
There are several main 'flavours' of PackageManagementTool in use in various LinuxDistribution. These include:
; __rpm__ : RedHat [Package] Manager. Obviously, RedHat uses this, but [Mandrake] and a handful of others do as well. File format is [RPM].