This is similar to #2222, but I read the conclusion there as "the RPM team
won't bend over backwards to support an OS that isn't POSIX complaint," which
makes perfect sense to me. Now, macOS has added the missing POSIX function
described in that issue, but 4.20 won't build for different reasons:
* #2046 now requires a GNU extension `GLOB_ONLYDIR`
* #2249 now requires a GNU extension `strchrnul`
* [elfdeps target links against libelf from
elfutils](https://github.com/rpm-software-management/rpm/blob/rpm-4.19.0-release/CMakeLists.txt#L416),
but elfutils is Linux-only. I can't quite follow exactly how this was
introduced, maybe #2302
* And possibly a few others. (I'm getting this list of examples from
[here](https://github.com/orgs/Homebrew/discussions/4826#discussioncomment-7779025).)
The discussion for #2046 even acknowledges that it'll break POSIX compatibility:
> Portability sucks, for the developers. If this becomes an actual issue, we'll
> look into integrating gnulib rather than maintaining our own copy.
It sounds like the Homebrew team has basically given up on trying to build rpm
for macOS, so I wanted to open this issue to clarify if that's warranted or
not. If we should expect every new version to break POSIX compatibility, then
I'd agree that probably makes sense. But I'm not sure if that's the actual
intent?
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2807
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/issues/2...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
