On Sunday, 16 June 2013 14:14:17 CEST, Pali Rohár wrote:
Ok, so if I choose QtKeychain for implementing gsoc kwallet support, there could be problem with packaging. But benefit is support for Apple & Gnome. If I choose kwallet library directly, there will be no packaging problems, but it does not support Gnome secure storage yet. But in future there could be one.
Right, it looks like QtKeychain does everything we require. What about the following, then: - if there's no QtKeychain at build time, disable password storage altogether and have Trojita ask for one when needed (the PWs shall still be "remembered" in memory while the session is active) - if QtKeychain is detected and enabled, use it and don't support any other password storage (but still store it in memory) When done properly, it should be possible to override the automagic dependency resolution via a flag to qmake/cmake to make packagers happy.
There could be another problem with QtKeychain library. Similar to contacts. If user change desktop QtKeychain can use another password storage (e.g kwallet is not running but secure storage yes).
Understood. In my opinion, this is the cost which the distro hoppers have to pay for now. If someone sees a problem with this approach, now it's the time to speak up. With kind regards, Jan -- Trojitá, a fast Qt IMAP e-mail client -- http://trojita.flaska.net/
