Am 11.02.26 um 18:29 schrieb Andreas Sturmlechner:
Stuck on QT5. Endangered by the QT5 purge. Needs porting to QT6.
I have close to no GUI programming experience so I do not think
I will have the time to do the qt6 migration upstream.
I would prefer to keep using keepassxc even if that meant
maintaining it. Does it make sense for me to step up?
Fixes to packaging can be made irrespective of you registering as maintainer,
and upstream currently do not give you anything else to work with. As long as
they don't deliver future prospects, or *you* come up with the Qt6 porting
commit yourself, I don't think it makes sense.
There is a long-running PR (~4 years) about the QT6 port in the
keepassxc github project:
https://github.com/keepassxreboot/keepassxc/pull/11651
I gave the respective source a try to compile, last ebuild compiles with
minimal modifications and the resulting binary is running. I did not
test too much yet, basic functions like database usage and editing or
interaction with the browser extension are working.
So I think it possible to change the ebuild soon to qt6. I can offer to
take proxy-maint the package, like many others I saw in danger to be
tree-cleaned.
martin
