Quoting myself from
https://github.com/rpm-software-management/rpm/pull/1470#issuecomment-772410935:
> That said, what little background processing I've managed to do on this, the
> more I think this isn't a use-case we'd want to be maintaining going forward
> in rpm itself.
I could've sworn I made it far more explicit than this, but then maybe it was
in some other context.
In any case, lets at least make it clear up-front this time: this functionality
is not something we want to maintain in rpm. So NAK on rpm2extents and the
reflink plugin, they will need to be maintained separately. The goal of
enhancing the librpm and plugin API's to make this all possible is okay, as
said before.
I noticed you asking about the plugin API in the discussion, sorry for not
replying there. But saying "not quite what I had in mind" would require
explaining how exactly to do that, and I haven't got cycles for *that*.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2378#issuecomment-1411912184
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/pull/2378/c1411912...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
