Hide Forgot
If I have some personal path settings during time of ``rpm -ba rpm.spec'', these very personal paths find their way into the deployed /usr/lib/rpm/macros. So everybody ``inherits'' these paths, which are of course generally wrong at rpm-runtime. Default path settings for the target platform have to be used instead. This is another situation, where a class model for hardware-platform, operating system and distribution would clean-up the situation. Then the ``distribution''-object would provide all the paths for its system utilities [+ some other properties].
Control for your path when building rpm. Otherwise, correct your configuration after building. Eventually, paths to executables will be in static per-platform configuration, but there is as yet insufficient need or utility in undertaking that effort.
This is an rpm configuration issue, and there is certainly sufficient mechanism already within rpm to control for paths to executables if you define macros in ~/.rpmmacros and/or /etc/rpm/macros