From Fedora Project Wiki

(fix links)
(one more)
Line 44: Line 44:
* Software installed from source will not upgrade with package managed packages, leading to breakage in the source install package on upgrades or os updates.  
* Software installed from source will not upgrade with package managed packages, leading to breakage in the source install package on upgrades or os updates.  


Strongly consider making your own package if you need a different version or a version of some package with changes. See: [ how to create an rpm package http://fedoraproject.org/wiki/How_to_create_an_RPM_package]
Strongly consider making your own package if you need a different version or a version of some package with changes. See: [http://fedoraproject.org/wiki/How_to_create_an_RPM_package How to create a RPM package]


== Package Management tools ==
== Package Management tools ==

Revision as of 20:07, 23 December 2010

Package Management System

Introduction

Fedora is a distribution that uses a package management system. This system is based on rpm , the RPM Package Manager, with several higher level tools built on top of it, most Notably PackageKit (default gui) and yum (command line tool).

Advantages of package management systems

Package management systems have many advantages:

  • It's easy to query what version of a package is installed or available.
  • It's easy to remove a package entirely, making sure all it's files are gone.
  • It's easy to verify the integrety of the packages files, so you can see if it's been corrupted or tampered with.
  • It's easy to upgrade a package by installing the new version and removing all the old versions files. This will make sure not to leave any lingering files from the old package around to confuse or break things.
  • It's easy to see what packages require or provide things that other packages provide or require, so you can be sure to have the needed

items for the package to function correctly.

  • It's easy to install or remove groups of packages.
  • In many cases it's possible to downgrade back to a previous version of a package, for example when a new version has a bug.

Disadvantages of package management systems

  • You are restricted to either using the versions of the package that are available or having to make your own package if you need a different version.

Why mixing source installs and packages is a bad idea

Package management systems have no way to query or note when you bypass them and install something from source. You should avoid mixing source installs and packaged installs for (at least) the following reasons:

  • You lose all the advantages above from a package managed system.
  • Installing from source may overwrite, delete, or change existing files that are in a package, making that package not function correctly.
  • The source install may override a package install causing undefined behavior in the package or source installed item.
  • Installing from source makes it impossible or very difficult for anyone to help you debug issues, since versions can't be easily queried and integrety checked.
  • Fedora packages may have patches or configuration to work with other packages, but upstream source does not, leading to loss of functionality.
  • Software installed from source will not upgrade with package managed packages, leading to breakage in the source install package on upgrades or os updates.

Strongly consider making your own package if you need a different version or a version of some package with changes. See: How to create a RPM package

Package Management tools

yum

PackageKit

rpm

yumex