RPM has only path and directory dependencies, largely because the path
canonicalization in rpmCleanPath() always strips a trailing '/' character.
Luckily, the (arguably hacky) fix is not very complicated.
1) always over allocate paths by 1 byte to accomodate a trailing '/' (if
necessary.
2)
--
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/439___
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
This makes it possible for a package to do:
Requires: system(EFI)
or
Conflicts: system(EFI)
I'm certainly open to other ways to do this, or other ways it needs to be
phrased.
You can view, comment on, or merge this pull request online at:
Good.
Meanwhile I suggest you look at the refactored lib/rpminstall.c
tryReadManifest(). There is no logic there preventing the call.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
THANK YOU FOR THIS. :+1: :hearts:
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Closed #437.
--
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/437#event-1596384016___
Rpm-maint mailing list
May be one could construct a package with only the modified (and config) files
in the payload. That might only require very minimal changes on the rpm side.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
The idea here is to not copy the unchanged files at all. So to not only save
the compression but the moving around of most of the data. Sure, we would still
need to read and check sum them (twice probably). Yes, this is inherently more
risky than reconstructing the original package. But it is
