Several points:
1) Your check for repackaged packages is what is running afoul of (what is
obscurely known as) a "dribble", a tag appended to an immutable region, which
is commonly found in repackaged packages (with a doubly linked upgrade chain
tag appended) and in rpmdb headers (signature tag
Presumably you are talking about an rpm macro since there are already C macros
in .
I fail to see how knowing machine endianness in an rpm macro assists with
packaging: patches could (and likely SHOULD) be written to include
and test with a C macro rather than optionally applying a patch.
If
TL;DR The 2nd headerReload() appends RPMSIGTAG_PADDING into a contiguous
PROT_READ block.
--
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/270#issuecomment-348756410__
Note also that adding an additional "informative" rpm macro to distro
configuration is utterly trivial (if that is all you wish) and documenting the
usage in distro packaging policy building a usage case.
Magically (and portably) detecting endianness within rpm build is trickier:
consider cross
What's the status here? I just ran into this because I'm trying to upgrade lua
to 5.3 in Homebrew. It would be good not to have to force 5.3 to build with
LUA_COMPAT_MODULE enabled, since that somewhat defeats the upstream purpose of
deprecation.
--
You are receiving this because you are subsc