If you don't want to link to librpm, then other option is to use rpm cli.
Everything about the packages is accessible with rpm cli queries.
I don't understand your use-case, but if you absolutely need the package
information on file-system then create that info using rpm queries, as a part
of
Nope.
Is there a reason that using librpm is not an option? If there is, you will
need to reverse-engineer the format and keep pace with whatever librpm does.
Could you compile librpm to WebAssembly and create a new WebAssembly runtime
for each container? That could be a solution to
This restricts our use case (container vulnerability scanning): is there a
recommended way to see package information from the filesystem (like how Debian
has `/var/lib/dpkg/info/[PACKAGE].list` files)
--
Reply to this email directly or view it on GitHub:
