NAK for paths, it creates more problems than it solves.
Having rpm default to a modern dist-git style layout (or a trivial one-liner
way to enable it) would be more useful.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Closed #352.
--
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/issues/352#event-1469447590___
Rpm-maint mailing list
(aside)
There are ways to configure rpmbuild to do everything in the current directory.
I have published my macros configure file multiple times in the past 15 years.
Adding multiple directories and a search path to existing macros like
_sourcedir adds complexity for not much gain, and is quite
(aside)
There are ways to configure rpmbuild to do everything in the current directory.
I have published my macros configure file multiple times in the past 15 years.
Adding multiple directories and a search path to existing macros like
_sourcedir adds complexity for not much gain, and is quite
Most of the time I have to do `-D "_sourcedir $(pwd)"` and it is really
annoying that I can't set _sourcedir to something like
`%{_topdir}/SOURCES:%(pwd)` and RPM would search for both directories. Like a
PATH, LD_LIBRARY_PATH are working.
--
You are receiving this because you are subscribed