Thank you, JuanJo and Dev_Hopeful.
I believe you both answered my question. I will implement what you suggested. But let me clarify this, please: If I add <removefilesfromuninstaller> to preserve the sym link from being removed, then will the uninstaller still remove the "target" file? For example, will this be a correct graphical view, when X.1 and X.2 are both installed, and then X.1 subsequently uninstalled?
After uninstall of X.1 , provided that <removefilefromuninstall> was added to the Install script for <createsymlink>
What will happen when X.2 is uninstalled? Will the sym link be removed then, since no "targets" for it remain?
asked 08 May '12, 14:04
Sorry, just to make sure I understand the issue. You are installing two times the same application (or two applications sharing the same library) and a both create a symbolic links to the library under the installation directory.
In your first case you mentioned that deleting one of them deleted the link and made the other crash, but, it one link overrides the previously created one, even if the link is not uninstalled, as the library it points to is uninstalled, wouldn't it fail the same way? Why do you need to create the link? Would be possible to create a wrapper to your application that would define DYLD_LIBRARY_PATH pointing to you local libs?
That would save you all the trouble of trying to protect one installation from the other uninstallers
answered 09 May '12, 12:36