[Rpm-maint] [rpm-software-management/rpm] RPM with Copy on Write (#1470)
chantra
notifications at github.com
Thu Feb 10 19:05:17 UTC 2022
> As payload format is a per-package thing, this should be determined on rpmte level rather than per-file level
This is somehow what is being done here. In the psm_pre hook, reflink determine that the package is a transcoded one and is to be handled by itself. I understand this hook is at rpmte level.
> and the writing side needs to be something like rpm handing the plugin an open fd and the plugin placing the content there by whatever means
This is currently emulated by [providing an archive_reader hook](https://github.com/chantra/rpm/commit/1cc53396f73651a86f002b4db97d28329b85c176), that lets the plugin define how to iterate over each files (using header or content of payload). And then, for each entries, install of the files can be offloaded to the [plugin with the install_file hook](https://github.com/chantra/rpm/commit/ad46eb4132cbd2c4ee23686a1c52f2fc57afffc5). If nothing is performed by a plugin, it defaults to core RPM behaviour.
Does that somehow align? Any changes you like to see in how this is done? Shall I start a PR on top of https://github.com/rpm-software-management/rpm/pull/1909 with those new hooks?
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/1470#issuecomment-1035353657
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/pull/1470/c1035353657 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20220210/a91cdb83/attachment.html>
More information about the Rpm-maint
mailing list