After way too much procrastinating and indecision...
We wont be able to axe the internal parser in 4.19, dunno about 4.20. But
that's a long way off, and until then we need to support what we ship. To avoid
having to pile this complexity on and on and on to deal with subkey this and
subkey that, I think the only possible solution is to saw off the limb to save
the patient: remove the subkey support (#2278). That's where like 90% of the
complexities seem to be.
Clearly quite a bit of work has gone into this PR and I hate to throw that
away, but it's not like I didn't warn right from the beginning. As most of this
PR is dealing with subkey matters, merging it just to remove the added
complexity right after doesn't make any sense. Lest it all go to waste: at
least the bit to support Sequoia-generated keys deserve salvaging but that's
really unrelated and should be filed separately. Ditto for test-cases, but only
for the Sequoia backend. There may be others but lets first get the subkeys
out, it'll be clearer then.
Thanks and apologies, I should've been firm with this right from the start. I'd
like to claim the crystal ball on this all was still fuzzy in the spring but
that'd be lame.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/1993#issuecomment-1319665652
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/pull/1993/[email protected]>
_______________________________________________
Rpm-maint mailing list
[email protected]
http://lists.rpm.org/mailman/listinfo/rpm-maint
