Well, for this to happen we would first have to make sure OpenACS does install as an RPM (or did I miss something ?).
If you are knowledgable about RPM and dependencies you can most likely take the installation recommendations you find at https://openacs.org/doc/openacs-4-6-2/unix-install.html, amend them to support the various distributions RPM's for Postgres and AOLserver (or convince them to use our standards and compilation :)) and prepare a package for the OpenACS core that will install OpenACS in the appropriate directory and tweak AOLserver to listen at localhost:8000 for setup purposes. Furthermore load the data into the datamodell of the already created openacs user.
Once this is done, we would have to get someone to write a small script that offers the various packages as APM files for download from the website of OpenACS.org. And make it more comfortable to load these (e.g. just let the APM point to the location for the overview page and get a list like you get when you install the package) to your computer. Or you could make an RPM out of it that would install the files in the folder according to the standards set forth in the above section. My only concern would be what happens if you move your server to a different physical location (e.g. change /web/openacs to /web/myservicename).
To sum it up, there is a lot more involved than just creating RPMs for the distributions. And this is the reason why RPMs are so rare within the OpenACS domain.
