Yumie should be extended further to address the problems that every day users face.
Doing that is why Yumie is still not available. Remember that Yumie simply operates YUM, and YUM does not always return intelligent information when it fails, which means that Yumie would need to implement a lot of artificial intelligence to figure out what went wrong. A few of the more common failures are handled, but even then, it seems to be impossible to fix some problems. For example, all of my test systems complain that the RPM database is corrupted, every time I download something. There is really no problem, whatever it is gets properly installed, and all of the suggestions about how to fix the database don't fix the problem (which is probably not a database error anyway). It looks like the only answer is for Yumie to ignore the error, but doing that may miss a legitimate error.
Please tell me how the script should search the system to determine what should be left and what should be renamed. Feel free to provide functions to take care of whatever has to be taken care of and I'll try to glue it all together.
That is somewhat difficult. There are two major divisions. One is using RPM/YUM (with, or without, Yumie). The second is not using it (and there are many good reasons not to use it, but the main problem can still exist). Then there is a minor division, where a user has eComStation, or not. Less common, is where a user has made their own location to contain all of the RPM supplied DLLs (and that doesn't need to be on the boot drive). So, your script needs to determine if RPM/YUM is actually installed, and USED. Then, it needs to make the YUM stuff the first choice (if it is actually used), accounting for the user preference of the order of @UNIXROOT\usr\local\lib and @UNIXROOT\usr\lib (and they don't need to be on the boot drive). followed by what is in <bootdrive>:\OS2\DLL and <bootdrive>:\eCS\DLL (assuming that a user hasn't moved them around). All duplicates in any of those locations need to be resolved (there should be only ONE, and it should be the latest, but you can't depend on file size, or date, to determine that, and there is no bldlevel information, which should be easy to add, if those who supply the files would just do it. Then, you need to scan the rest of the system (ignoring alternate boot drives), and eliminate anything that is in any of those (call them "master") directories. Of course, you need to ASK the user what to do about duplicates because they may have a reason to keep something (which is okay, as long as they understand the consequences).
I want to emphasize a previous post about uninstalling the RPM/YUM WarpIn installer (using WarpIn), after running the initial YUM INSTALL YUM command. That command actually installs RPM/YUM, using a temporary, very down level, version of RPM/YUM. If you continue to use the "console", you will be using that very down level version, and it doesn't work very well. You need to use the standard command line window, or Yumie (when available) to use the updated stuff.