What is a RPM
RPM stands for Red Hat Package Manager. Red Hat created a package management system where coders could take their source code, compile it and package it a form that a user could install programs on their computer. The RPM Package Manager (RPM) is a powerful command line driven package management system capable of installing, uninstalling, verifying, querying, and updating computer software packages. Each software package consists of an archive of files along with information about the package like its version, a description, and the like.
One thing that seems to confuse new users to Linux is they see a RPM, try to install it and they see some kind of dependency error and have no clue as to what it means. Linux distributions build RPMS against installed libraries. This is called building with shared libraries. Building RPMS in this manner creates smaller programs and allows many programs to all share the same library files. The downside to this approach is many distributions use different libraries or different versions of these libraries. Thus if company-a builds a RPM against library-a and company-b builds the same RPM but against library-b, you wont be able to install the rpm from company-b on company-a's distribution. You should always use RPM's built for the distribution you are using.
- Login to post comments
- 2178 reads

Beyond RPM?
Linux is made of modules, which is compiled by list and script. Modules are often written by C++ language then compiled into native language and compressed. RPM is born of list of modules and scripts. But many in the RPM packages of application programs, are commandline software which lack upgrades. Debian had apt-get and dkpg packages with more modern, click and run gui front ends. Then there are kpackages from KDE, in window environment yet. Recently, tiny Puppy linux offered TCL(tiny Cobol) written static software as .pup and other package systems to their users. Where tiny Linux operating system can rival big name Linux distros. Interesting developments continue to happen in the open Linux community, but the trend is changing to Linux stanadardization; so the same Linux application peograms can be used by many distros. Package(as we know it) may be superceded by compiled static programs easily downloaded and added in your file manager. This reversal is actually progress from chaos back to sanity.
packages for linus distros?
Increasingly, package management inclusion distinguishes Linux distros. Mandiva added apt-get. Knoppix(Debian) has RPM. Linux distros have to compete based on the ultimate full blown capabilities. This means standardization of codes, and flavours. More and more, all presentation had to have design kits easily modified for all gui front ends. Dependency file version have more backwared and mutual compatibility. Filters to combine foreign codes in native modes. Wine, mono and others will be more popularly available. You probably will select the Linux distro that caters all application programs. I selected Knoppix so far; but others are coming.