severity 570331 wishlist
tag 570331 wontfix
thanks
On Thu, 18 Feb 2010 16:20:25 +1100
ian <[email protected]> wrote:
> Package: ejabberd
> Version: 2.1.2-2
> Severity: important
>
>
> At the command line:
> r...@mars:~# ejabberdctl export_piefxis /var/lib/ejabberd/
> Problem 'throw {error,exmpp_not_installed}' occurred executing the command.
> Stacktrace: [{ejabberd_piefxis,try_start_exmpp,0},
> {ejabberd_piefxis,export_hosts,2},
> {ejabberd_ctl,call_command,3},
> {ejabberd_ctl,try_call_command,3},
> {ejabberd_ctl,process2,3},
> {ejabberd_ctl,process,1},
> {rpc,'-handle_call_call/6-fun-0-',5}]
>
> This 'exmpp' package is not available in a Debian package.
Yes, this fact is mentioned in the section
"EXPORTING DATA TO PIEFXIS (XEP-0227) FORMAT" in the ejabberdctl(8)
manual page.
The problem is that:
1) All PIEFXIS commands are implemented by the mod_admin_extra
contrib module which is not a part of ejabberd.
2) exmpp is, strictly speaking, not currently related neither
to ejabberd nor to mod_admin_extra -- it's a standalone
XMPP library for Erlang written mostly in C; it's rumored to be
a base for the prospective 3.x.x line of ejabberd development,
but 3.x.x is currently far from being stable.
So, when I discovered PIEFXIS cannot be supported without presence
of exmpp, I pondered patching mod_admin_extra to disable these
commands. I decided this is bad because someone who really wants
these commands to work might opt to building and installing exmpp.
So currently it's just documented they won't work as is.
Of course, it would be much better to print sensible error message
when one of these commands is invoked for the current behaviour does
not hint the user to read the manual (but hints it to google for the
error which possibly leads to discovery of exmpp).
The problem is that I currently have no idea about how to implement
this.
As to packaging exmpp -- as I was said this library is largely
orthogonal to ejabberd 2.1.x, is of unknown stability and is not
currently required for any useful other Erlang software I'm aware of.
Hence I'm unsure I want to package and maintain it before ejabberd
3.x.x becomes the mainline of development.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
