mod_archive_odbc permits ejabberd to store conversation history on servir-side in MySQL/SQlite database. It is the greate avantage of jabber as compared to most other IMs. I think it is good idea to add this feature to ejabberd on gentoo. Reproducible: Always
Could you create tested patch for ejabberd, ebuild, for metadata.xml, please?
(In reply to comment #1) I can only write how to add mod_archive support manually: svn co https://svn.process-one.net/ejabberd-modules cd ejabberd-modules/mod_archive/trunk ./build.sh cp ebin/mod_archive.beam /usr/lib/erlang/lib/ejabberd-2.1.4/ebin/ # and if USE=web: cp ebin/mod_archive_webview.beam /usr/lib/erlang/lib/ejabberd-2.1.4/ebin/ mod_archive.beam and mod_archive_sql.beam is "old" accordng to http://www.ejabberd.im/mod_archive and mod_archive works for me without them.
sorry, after "./build.sh" must be coping mod_archive_odbc.beam instead of mod_archive.beam
As I read homepage: here are three different versions of this module. The main difference between them is the storage method: mod_archive uses Mnesia (old) mod_archive_sql uses PostgreSQL (old) mod_archive_odbc uses MySQL or SQLite3, and includes other improvements so we should use mod_archive_odbc. At the same time mod_archive_odb homepage (mentioned at http://www.ejabberd.im/mod_archive) tells us (http://www.ndl.kiev.ua/content/modarchive2-status): Update: development of this module has stopped, all further development is done in mod_archive2 project. It has sources at https://github.com/ndl/mod_archive2 and looks like last commit was done on 2009. I'm not sure we need old mod_archive and I'd like to hear if mod_archive2 works for you... Thoughts? Do we really need mod_archive?
Please, comment what module you use? Have you tried newer one? I'd like to avoid adding obsolete version...
