Again: my 1st suggestion was for a removal from git to avoid an annoying 
warning when the file (as always) is replaced by autoreconf.

I added historical context about why an otherwise generated file was added to 
CVS (at the time),
and have personally seen the annoyances that happen when otherwise generated 
boilerplate
ends up under source code control.

At the time I was also personally involved in maintaining RPM on HPUX and 
Irirx, on systems that were using modems for internet connectivity, and so I 
also added /usr/lib/rpm/mkinstalldirs to avoid the tedious task of fetching a 
copy of mkinstalldirs.

This was *NOT* a suggestion that
1) mkdir is portable so that mkinstalldirs can be removed everywhere.
2) mkinstalldirs should not be distributed in tarballs
3) there aren't portability problems between linux and other operating systems: 
both ways.

-- 
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-317474089
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint

Reply via email to