The OP has multiple interdependent installations - to get results he therefore needs a common library architecture.

So your comment about DLLs being local to a software component SUPPORTS my somewhat tentative accusation that Windows doesn't have it.

Update: To clarify, it might be theoretically possible to put shortcuts to or copies of all relevant DLLS in different places - but what is theoretically possible isn't nearly as strong as saying something is "feasible", especially if you think through properly all the nasty obstacles that could appear such as an undocumented DLL filename not being present for a component. The OPs successful effort succeeded in an rpm environment that manages dependencies properly - it should ring the right alarm bells if you consider the implication that it didn't work in environments where dependencies were not managed.