Skip to content
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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecate Berkeley DB backend and beecrypt support #1129

Merged
merged 3 commits into from Mar 23, 2020

Conversation

pmatilai
Copy link
Member

Both components are dead upstream for about seven years, deprecate them for later removal, now that we have alternatives.

Beecrypt upstream is dead for seven years, this is not a healthy situation
(death tends to have that effect...) for any component, and even less
so for security sensitive component. Deprecate for later removal now
that we have multiple nicer alternatives.
Berkeley DB 5.x is dead upstream ever since the license change some
seven years ago. Mark as deprecated for later removal now that we're
starting to have viable alternatives.
@pmatilai pmatilai added this to the 4.16.0 milestone Mar 23, 2020
@pmatilai pmatilai merged commit fc0169e into rpm-software-management:master Mar 23, 2020
@Conan-Kudo
Copy link
Member

@pmatilai Why didn't we just remove beecrypt? It's not like bdb where it has drastic consequences for users whether it's available or not, and with having libgcrypt, we don't need it anymore.

@pmatilai
Copy link
Member Author

pmatilai commented Mar 24, 2020

Trying to behave a civilized upstream for once, and deprecate features before removing? 😁

@pmatilai pmatilai deleted the deprec-pr branch April 3, 2020 10:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants