Having more modules does indeed complicate things, but then we're already in a
situation where we need to coordinate any API additions between rpm and
rpm-sequoia. It just hasn't really come up yet because ATM we're just bumping
the required rpm-sequoia version as we go, but at some point we'll probably
need to allow for more freedom (for older versions and such).
I basically see this as another step on our way to drop support for the
internal parser entirely, I have a hard time seeing the development on it
"taking off" due to the split. And if I'm proven wrong on that, then I guess it
shouldn't have trouble keeping up with the new APIs either.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2704#issuecomment-1750249919
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/pull/2704/c1750249...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
