We don't want to add a "proprietary" format for such a thing because standard
header APIs are then no longer usable for accessing and modifying it, and then
you only have more code to worry about. We could also just use hex strings,
size is not a concern here. But, if we can't be trusted to decode base64 then
how are we expected to read the rest of the rpm? That's like being too afraid
to leave the house because something bad might happen. I'll note that this
*is* something that could be easily outsourced to rpm-sequoia.
Binary arrays could be sort of handled with existinging code u,sing an embedded
header (it's just another binary blob afterall), using tag number as the index.
But this gets weird and wacky and it's not like the header itself is a trivial
structure to parse.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/3385#issuecomment-2425724153
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/issues/3385/[email protected]>
_______________________________________________
Rpm-maint mailing list
[email protected]
http://lists.rpm.org/mailman/listinfo/rpm-maint
