Hmph, there's an elephant or two in the room. Of course there is...
There are two major cases unresolved by this: fingerprinting, and rpm -V
verification. Fixing verify is merely annoying, but fingerprinting is much
harder and more intrusive as there are several far-apart places where we stat()
stuff.
However those are always read-only accesses, which seems to be mostly harmless
and nothing seems to mind. The cases where it matters are open, close and
writing.
So at the very least, the commit message needs to clarify the chroot rules
being laid out here, and that's what this is largely about: while rpm itself
can generally be fixed to function on whichever side of chroot, that's not the
case for external libraries we might call, and there's also our own API users
and *their* external libraries that can be affected by all this.
--
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/836#issuecomment-533042740
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
