Penguin
Diff: PackageManagementTool
EditPageHistoryDiffInfoLikePages

Differences between version 23 and revision by previous author of PackageManagementTool.

Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History

Newer page: version 23 Last edited on Tuesday, November 2, 2004 3:29:37 am by AristotlePagaltzis Revert
Older page: version 21 Last edited on Monday, February 2, 2004 7:30:17 pm by PhilNewcombe Revert
@@ -1,15 +1,23 @@
-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. 
+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].  
-; __ dpkg__ : This is [Debian]'s [Package] manager. KnoppixLinux, [Progeny] and other [ LinuxDistribution] s are "Debian-based" and thus use this as well. File format is [Deb].  
-; __ .tgz__ : [Slackware] uses nearly plain [ TarBall] s that include a description and a postinstall script.  
-; __ ports__ : This is the source based PackageManagementTool that [BSD] uses. Several [ LinuxDistribution] s use a similar idea.  
-; __ portage__ : [GentooLinux ]' version of source based PackageManagement, driven by a tool called __ emerge__ .  
-; __spells__ : Sorceror Linux has a 'spell book' approach to source based PackageManagement. 
+<tt> rpm</tt> :  
+ RedHat [Package] Manager. Obviously, RedHat uses this, but [Mandrake] and a handful of others do as well. File format is [RPM].  
+<tt> dpkg</tt> :  
+ This is [Debian]'s [Package] manager. KnoppixLinux, [Progeny] and other LinuxDistribution~ s are "Debian-based" and thus use this as well. FileFormat is [Deb].  
+<tt> .tgz</tt> :  
+ [Slackware] uses nearly plain TarBall~ s that include a description and a postinstall script.  
+<tt> ports</tt> :  
+ This is the source based PackageManagementTool that [BSD] uses. Several LinuxDistribution~ s use a similar idea.  
+<tt> portage</tt> :  
+ [Gentoo ]'s version of source based PackageManagement, driven by a tool called <tt> emerge</tt> .  
+<tt>spell</tt> :  
+ Sorceror Linux has a 'spell book' approach to source based PackageManagement. 
  
 Frontends to these tools include: 
  
-; __up2date __ : a front-end to rpm provided by RedHat. You get to use it on one machine per user free, and can pay for the right to use it on more machines. It's probably worth it for most users, as it makes installing new software and keeping up with upgrades really easy.  
-; __ [APT]__ : one of the best tools around. It traditionally wraps dpkg, but there is an AptForRpm variant now (and rapidly gaining popularity). It was the first front-end to nicely handle dependencies: __ apt-get install foo__ will automatically download and install not only __ foo__ , but also any unfulfilled dependencies __ foo__ may have. There are lots of supplemental utilities surrounding -- see DebianPackageTools. 
+__Up2date __:  
+ A front-end to rpm provided by RedHat. You get to use it on one machine per user free, and can pay for the right to use it on more machines. It's probably worth it for most users, as it makes installing new software and keeping up with upgrades really easy.  
+[APT]:  
+ One of the best tools around. It traditionally wraps dpkg, 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.