The whole idea that absolute paths need to be provided as macros to be expanded
in spec files has been unnecessary since POSIX was invented and widely deployed.
When was the last time you felt the need to write a shell script that used
absolute paths for common system programs? The entire reason for supplying
macros with absolute paths was to simplify *MY* life developing RPM on Solaris
last century with GNUish utilities in /usr/local/bin and BSDish utilities in
/usr/bin. With POSIX utilities everywhere, PATH should be used, because, well,
that is what one does in uglix.
As for OpenMandiva, part of switching from python2 to python3 is to ensure that
the executable called "python" Does The Right Thing.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/508#issuecomment-412704987
_______________________________________________
Rpm-maint mailing list
[email protected]
http://lists.rpm.org/mailman/listinfo/rpm-maint
