Bug 620618

Description of problem:
Gwibber currently relies on Desktopcouch, CouchDB, which relies on a large number of Erlang packages.

The current CouchDB version is slow and prone to resource consumption problems. An alternative branch for Gwibber was developed to port to SQLite for the storage backend

It would be nice to have this added to Rawhide to give option to test as long-term alternative to the current Gwibber backend CouchDB

Version-Release number of selected component (if applicable):

gwibber/230-sqlite-backend

Additional info:

http://gwibber.com/blog/
CouchDB and SQLite backends

Gwibber 2.30 uses Ubuntu's DesktopCouch framework so that it can its message cache, accounts, settings, and other relevant information inside of a local CouchDB database. Although DesktopCouch offers a lot of compelling advantages, such as seamless synchronization, it has some performance limitations and is difficult to package.

Users who do not want to rely on CouchDB can instead use Gwibber's SQLite backend. This alternate storage backend obviates the DesktopCouch dependency and also offers improved performance and stability. If you want to run Gwibber with SQLite, you can obtain it from the 230-sqlite-backend branch on Launchpad. I am currently working to integrate this alternate backend directly into the latest code in Gwibber trunk so that it will be easier to maintain it alongside the existing CouchDB backend.

In future versions of Gwibber, SQLite will be used by default for all message caching. CouchDB will be used for storing accounts if it is available, with the ability to automatically using SQLite instead as a fallback when DesktopCouch is not installed.

https://code.edge.launchpad.net/~segphault/gwibber/230-sqlite-backend