Merged #275.
--
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#event-1181622775___
Rpm-maint mailing list
FWIW, I have *repeatedly* argued for native (i.e. --prefix=/usr, etc etc)
installation on OS X to no avail.
I have also successfully ported and run RPM on OS X for many years.
Meanwhile I return to my original statement:
> ... there are no efforts to port RPM to OS X (or Mac OS) natively ...
Conan-Kudo approved this pull request.
--
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#pullrequestreview-51944039___
@n3npq I've been working on it, fwiw.
--
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-317480020___
Rpm-maint
Specific to OS X portability: there are no efforts to port RPM to OS X (or Mac
OS) natively (i.e. using only utilities that come from the OS vendor) that I am
aware of for ~15 years. All existing porting efforts involve Fink, MacPorts or
Homebrew, and so "portability" includes duplicating
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
So today, the problem isn't that `mkdir -p` doesn't exist, but at least on my
Mac (running macOS Sierra), it seems to fail the test by autoconf, so it's used
in place of `mkdir -p`. I don't know if upstream BSD mkdir improved enough to
pass the autoconf check, as I don't have a FreeBSD system
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
@n3npq I think it was said recently in some other PR that it's still needed for
some ancient platforms which we (are we?) support..
#205 it was
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
You might just as easily drop mkinstalldirs. The original motivation for
including mkinstalldirs was from last century: certain ancient SysV non-linux
platforms lacked "mkdir -p". Carrying mkinstalldirs was the solution.
--
You are receiving this because you are subscribed to this thread.
There are no changes really in new version, but annoying when doing autoreconf
-vfi locally and always I get changes in this file...
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
11 matches
Mail list logo
