Comment 5 for bug 930471

The Rsourcedir -> Lsourcedir is unidirectional and driven by logic
of non-existence in Lsourcedir.

If you are disabling fetching, then you are expecting something different
from Rsourcedir than what is implemented.

Whether a macro is file-based like
   %{load:/path/to/somewhere/file}
or configuration like
    %oad:%{_somemacro}/file}
is entirely contained in how one chooses what macros to use. I
chose to illustrate with file paths.

At the end of the expansion -- and in expanded *.spec which you seem to want --
it ends up as a file path, so that I/O can be performed on the build machine.

ALl "caching" schemes are store-and-forward and involve rewrites of remote
paths to local paths, usually directories, with file names remaining constant.
That is what is implemented with %_Rsourcedir -> %_Lsourcedir and if
you have disabled fetching, then the store-and-forward mechanism
implemented in rpmbuild is useless, and you are likely better off designing
in your own macro configuration, and re-configuring rpm build to use your
\configuration rather than expecting %_Rsourcedir to do what isn't implemented.

Good: rpm-5.2.2 is mostly end-of-life these days.

rpm-5.3 is "production", rpm-5.4 is "development" and differs hardly at all from rpm-5.3
atm. I can neither here nor see your "noise and knock", bumping an rpm version is
a rather quiet operation.