[Rpm-maint] [rpm-software-management/rpm] RPM with Copy on Write (#1470)
chantra
notifications at github.com
Mon Feb 14 19:14:13 UTC 2022
The discussion/feedback that have been going on recently were very useful, but I would like to re-focus the original intent of this PR so we can make progress moving forward.
@pmatilai , @ffesti how would you like to proceed with this?
>From my end, I see a few individual chunks that would help in getting stuff out incrementally without it being a big change.
- rpm2extents change: This is the program to use in the pipeline to transcode the rpm into a RPMCoW-enabled rpm. This is mostly a standalone change, the only place where it touches rpm is to be able to leverage the existing signature verification logic. It also need the new `rpmReadPackageRaw` and having `pgpStringVal` to match digest algoritm from a string passed as an argument.
- improve plugin API
- Decouple from rpmRC (#1909)
- handle the `RPMRC_PLUGIN_CONTENTS` logic, e.g being able to have a plugin stop the plugin chain rather than iterating over single plugins.
- add new hooks when [installing files](https://github.com/chantra/rpm/commit/ad46eb4132cbd2c4ee23686a1c52f2fc57afffc5) and when getting a [rpmfi](https://github.com/chantra/rpm/commit/1cc53396f73651a86f002b4db97d28329b85c176)
- with the plugin API above, we will be able to integrate `reflink` as a plugin and not interference with RPM core.
I believe if we were to address the 3 items above in individual PRs, it will be easier to digest this original PR, iterate through each individual items to come up with something that we are all happy with.
Any suggestions?
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/1470#issuecomment-1039456158
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/pull/1470/c1039456158 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20220214/e71b4f1e/attachment.html>
More information about the Rpm-maint
mailing list