There are 3 issues:
1) mkdir -p isn't portable and so mkinstalldirs is needed
2) mkinstalldirs is distributed in /usr/lib/rpm
3) mkinstalldirs is copied and tracked in git or other VCS
My comment was wrto issue #3: mkinstalldirs was originally added to RPM in
order to assuage the bosses reluctance to use autoconf etc.
I suspect that /usr/lib/rpm/mkinstalldirs is seldom used, and there are
zillions of copies for those platforms that might need: distributing everywhere
to please a few oddball platforms (OS/2? Windoize? OS X?)
And the correct fix for racy mkdir breaking parallel builds (as described in
the autoconf doc cited in pull #205) is to go fix GNU mkdir like install -d (if
not already done long ago).
*shrug* removing mkinstalldirs from git changes almost nothing and does fix
your annoyance with autoreconf modifications.
--
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/275#issuecomment-317393813
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
