replace can not work in Fedora anyway because it is not transitive (it’s the kind of broken by design idea people invent when their primary target is to bundle piles of junk and avoid fixing their code).

source code that uses replace needs patching to use the real module/import name with or without modules. We have %patch and (soonish) patchlists for that, not sure a macro would be a lot more convenient, and it would certainly be more brittle.

Agreed that it looks messy. But in this case replace just means redirection and some name overlapping. Or maybe there should be some notes in Fedora's packaging guidelines to instruct the best practice to handle this?

rpm dependencies are transitive. That means replace can not be supported in rpm. That means the only sane way to handle replace is to remove it by patching code imports (which is not long or hard)

As to why non-transitive deps and 'to hell will everyone else, I only care about by own leaf node' approaches are a false good idea see the discussion on modules in devel right now. You win a little short term, you lose a lot long term as soon as the deferred technical debt catches up with you (as it caught up with the java module experiment).

Yeah. Not trying to really support replace but was asking how to deal with such case is acceptable and right for Fedora.
Now I know that just to replace the goipath to its real one by patches. Thanks for answering!