Suggested Enhancements to rpm

in section 2.1 we outlined the problems trying to support different distributions with rpm. In this section we outline a list of enhancements that could be made to rpm to improve its utility in handling multiple distributions.

• Dynamic file to package mapping. It would be extremely useful to have rpm install certain distribution specific files to an innocuous location (e.g. /tmp) and later relocate or delete them as appropriate in the %post section. The remaining files should show up in the rpm inventory in their new location.
• Dynamic dependencies. Since distribution dependencies are not always known at package build time, it would be useful to be able to modify them in a special section of the %pre script and have the system act on all the dependencies including the newly added ones. In addition, the ability to specify conditional or boolean logic in package dependencies would be useful. For example, a package could depend on one package name and version on one distribution, while depending on a different package on another distribution. Or perhaps a package could depend on one of two possible required packages.
• Scripted Interaction. Could do with an acceptable input method (which would be standard for the graphical install tools as well) which would allow the user to enter responses to a series of questions. The responses should be capable of taking default input from a file (so that the install may be customised for non-interactive non-default installs).
• Multiple file ownership. It would be helpful if the rpm model permitted more than one package to `own' a file. Often we get into the situation where we need to deliver a particular file, which may also be delivered by another, optional, package.
• Ability to install missing dependencies. In addition to having rpm list all the required dependencies, it would be useful to be able to have it install the missing ones from a pool of available package files.