Shortcomings of RPM Things I'd like to see in a downloadable package file that RPM doesn't do I'm thinking a separate APM (Application Package Manager) would be ideal...

It would be a "meta package" management system. I.E. a package file encapsulating a list of packages to be automatically installed based on the system in order to successfully create an installation

When I download a package file it should have these features:

• Ability to just click on it or type the package filename into a terminal and start a graphical (GUI) installer.
• Installer should be able to run regardless of precise linux distribution. The same application package file should work for Mandrake, SuSE, etc.
• RPM files can be used for the individual resources the application needs, but the installer must be able to add them without user manually downloading each.
• Installer must be able to resolve all dependencies
  
• It must be possible to embed all dependencies in the APM file
• It must be possible for certain dependencies to be resolved by downloading needed files from a supplied list of mirrors+file locations instead
• It must be possible to use vendor media, i.e. provide the user the option to insert one of their distribution's CDs or use the OS vendor's ftp site
• Installer should be able to fetch patches
• Installer should be able to provide mirror lists
• Installer should integrate some component so the user can uninstall it from an "Add/Remove Programs" list somewhere
  

  ¶ 8:13 PM