next up previous contents index
Next: An Overview of Dependencies Up: RPM and Developers - Previous: Conditionals   Contents   Index


Adding Dependency Information to a Package

Since the very first version of RPM hit the streets, one of the side effects of RPM's ease of use was that it made it easier for people to break things. Since RPM made it so simple to erase packages, it became common for people to joyfully erase packages until something broke.

Usually this only bit people once, but even once was too much of a hassle if it could be prevented. With this in mind, the RPM developers gave RPM the ability to:

In addition, they made sure RPM was able to display dependency information, as well as to warn users if they were attempting to do something that would break a package's dependency requirements.

With these features in place, it became more difficult for someone to unknowingly erase a package and wreak havoc on their system.



Subsections
next up previous contents index
Next: An Overview of Dependencies Up: RPM and Developers - Previous: Conditionals   Contents   Index
converted to HTML by Tim Riker