
At its 10th anniversary and after a period of uncertainty for the RPM community, together with a
new roadmap towards version 5.0 the project environment of the popular Unix software packaging tool RPM Package Manager was relaunched under the domain
rpm5.org by the newly formed RPM project team, further on lead by RPM's primary developer Jeff Johnson. The primary goals of RPM 5.0 are the additional support for the XML based archiving format
XAR, an integrated package dependency resolver, further improved portability and extended cross-platform support.
Note: Please note that rpm5 is a fork of the 'real' rpm project.
Member since:
2005-11-11
I was just about to predict that the first few posts will be about RPM dependency hell and how Debian rules.
When will you people learn the difference between a package format and a dependency resolver? They're two different things, and are not mutually exclusive.
- .RPM is like Debian's .DEB. It's just a file format, and the standard package manager doesn't do any dependency resolving.
- Debian's APT is like RPM's yum, or RPM's APT (!). APT is a program, built on top of a packaging file format, and provides dependency resolving capabilities.
APT can be, and is, used in combination with RPM. See http://freshrpms.net/apt/
All modern RPM-based Linux distributions have a dependency resolver, similar to APT. For example, yum on Fedora, urpmi on Mandriva, etc. This has been the case for more than 3 years now.
RPM and DEB are technically very similar. Neither is really superior to the other. The only difference is that Debian repositories tend to be larger than RPM repositories, but that has got nothing to do with technical merits.
Edited 2007-05-30 10:42