Thus far the only solution I have heard was the use of the UML kernel, which equates to allowing the users to run a virtual machine environment with the particular set of blessed rpm's for a particular development cycle. This in turn is kind of an extreme change rooted environment solution. The avenue I would really like to explore though would be to have the set of RPM's installed to a false root, but via changing environment variables and perhaps some wrapper trickery use the tools in the alternate root representing the development set for a particular release. The one issue I am still stuck with is how to make the the executables that are not linked static not use the shared libraries in /lib and /usr/lib, but instead use the ones in /false_root/lib and /false_root/usr/lib? Any thoughts on this? Thanks...james _______________________________________________ Redhat-devel-list mailing list Redhat-devel-list@redhat.com https://listman.redhat.com/mailman/listinfo/redhat-devel-list
