New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove deprecated beecrypt and NSS crypto backends #1245
Remove deprecated beecrypt and NSS crypto backends #1245
Conversation
Beecrypt whose upstream is dead for more than ten years now, was deprecated in rpm 4.16 (in commit 0910e6a).
馃殌 馃憤 |
Flushing BDB down the same drain is really, really, really tempting 馃槆 but maybe not just yet... |
@pmatilai I think we need to deprecate it in 4.17 and ditch it in 4.18 while keeping bdb_ro only. |
Actually BDB too is already marked deprecated in 4.16 (commit fc0169e) |
@pmatilai oh, in that case - I would ditch bdb backend and possibly enable bdb_ro by default for 4.17 and then in 4.18 disable it by default. |
@pmatilai Come on, drop BDB! Go for the gold! 馃 |
NSS is a behemoth of a library which drags in a whole runtime subsystem of its own which is often at odds with normal Unix system behavior (hello SIGPIPE). Now that we have nicer alternatives available there's little reason to lug this baggage along. NSS was deprecated in rpm 4.16 (commit 0b9efb9).
There's at least one thing that needs to be dealt with one way or the other before dropping BDB can be seriously considered:
However 4.17 will NOT ship as BDB as the default, no matter what. |
Anyway, the DB discussion is a separate topic. Thanks for the doc review guys, fixed in the last push. |
Shedding some weight to celebrate the beginning of a new cycle 馃巻