On 6/28/2010 1:43 PM, R P Herrold wrote:
All RPM needs is for people to read and use the tools, and all this is done well presently
What's the right approach with RPM to have multiple versions of an application installed simultaneously?
"Those who don't understand UNIX are condemned to reinvent it, poorly." – Henry Spencer
Yes, but unix was developed from the beginning with the idea of having test and production instances installed simultaneously and different users having their own different local copies of libraries and executables. It is RPM that doesn't understand those concepts.
And while you are at it, what's the right approach for using RPMs that are developed without coordinating their namespaces with all other potential sources of RPMs.