On Wed, Jun 24, 2020 at 06:51:36AM +0000, Zbigniew Jędrzejewski-Szmek wrote:
I think there's some fear that "name mangling" is not a
solution, and we'd have cases where names conflict. I think the
concern is realistic, but not a big issue in practice. With some
careful naming guidelines we are able to resolve naming conflicts, and
I'm sure we could extend the guidelines to multiple versions of language
stacks or whatever. We'd probably have slightly longer names or packages,
but that's not the end of the world.
Namespacing RPM package names is only a tip of the iceberg. You need to
namespace RPM requires, provides, shared library sonames, shared library
symbols, header files, header file symbols, pkg-config files, manual pages,
cross references in the manual pages, executable names etc. You need to
namespace everything if you aim for a parallel installability. That's the
reason why modularity does not tackle it and instead conflicts the concurent
versions by filtering the packages from the concurent streams.