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
Merged #274.
--
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/274#event-1176290736___
Rpm-maint mailing list
Closed #259.
--
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/259#event-1175541987___
Rpm-maint mailing list
Looks like mjw found commits which are already in upstream and fixing issue...
f0a58d1dced6215b7caaa70db17d54834e0cd44e +
3c74e34e8d8c5b3db024dbe04a352e807ed2b627
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@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
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___
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 ...
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:
You can view, comment on, or merge this pull request online at:
https://github.com/rpm-software-management/rpm/pull/274
-- Commit Summary --
* Add man page for systemd-inhibit plugin
-- File Changes --
M doc/Makefile.am (1)
A doc/rpm-plugin-systemd-inhibit.8 (36)
-- Patch Links
Signed-off-by: Igor Gnatenko
You can view, comment on, or merge this pull request online at:
https://github.com/rpm-software-management/rpm/pull/275
-- Commit Summary --
* update mkinstalldirs to latest version (2009)
-- File Changes --
M mkinstalldirs (9)
I would share a case I want you to upload the the rpm Python bindings to PyPI.
A python package `rebase-helper` [1] depends on the rpm Python bindings.
For this reason, `rebase-helper` can not add `install_requires` to `setup.py`
file.
If we want to install `rebase-helper` from source, I am
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
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/274#pullrequestreview-51745852___
@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:
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
17 matches
Mail list logo