On Wed, 14 Aug 2013 16:30:49 +0200, Stefan Sperling wrote: > On Wed, Aug 14, 2013 at 04:07:07PM +0200, Pascal Stumpf wrote: > > I have a patch for mcabber, see: > > http://www.isbear.org.ua/hg/isbear/mcabber-patches/file/tip/use-otr-v4.diff > > Great, so we now have patches for both bitlbee and mcabber. > I think we should get them tested and move forward. > > It seems Linux distros have resorted to keeping two versions > of libotr around... I'd rather avoid that if possible. > > > There's ongoing work for bitlbee: > > http://bugs.bitlbee.org/bitlbee/ticket/1004 > > I've written a patch for it, too, see my reply to jirib. > > > > - net/climm still packages, but I don't know if it works > > > > It does not detect libotr at configure time, so OTR doesn't work. > > So it's already broken anyway?
Err, no, it works with libotrv3, but doesn't detect libotrv4, so it builds fine, but without OTR support. > > That's pretty much an essential feature for me. I haven't yet figured > > out the transition to the libotrv4 API, so the update must wait (but > > feel free to give it a try; docs are available at > > http://www.cypherpunks.ca/otr/UPGRADING-libotr-4.0.0.txt > > Thanks for the link. The bitlbee changes were quite trivial. I got > all info I needed by comparing the libotr 3 and 4 header files. > >
