Gregory's Server
@ubernostrum you seem to mistake there's no going back for something it isn't but it means the situation was untenable.
I do not have a problem offering an explicit choice between a keepassxc-minimal and a keepassxc-full package.
Anyway, right now, keepassxc packages the default build flags, and keepassxc-full passes the option to turn additional features on. We're not at the outrageous territory where we need to take defensive measures by patching code, yet anyway.
@juliank @tuxwise @keepassxc The situation is untenable because you made it that way. You have decided that you know better than upstream.
This is sadly something that Debian maintainers have a history of doing with many projects, not just this one, and has caused many headaches for upstream maintainers who only find out from the deluge of bug reports that Debian broke their software.
Debian should not in general do that and you personally should not do that. You should package something that would cause the least surprise to someone migrating onto your package from an installation performed some other way. Or, if you are not willing to do that, you should step down and make room for someone who will do a better job.
@juliank @tuxwise @keepassxc The situation is untenable because you made it that way. You have decided that you know better than upstream.
This is sadly something that Debian maintainers have a history of doing with many projects, not just this one, and has caused many headaches for upstream maintainers who only find out from the deluge of bug reports that Debian broke their software.