[OTR-dev] 4.0.0-rc3 ready to roll. Please try it out!

[Ian Goldberg]

On Thu, Aug 30, 2012 at 05:02:57PM -0400, Paul Wouters wrote:
> In Fedora/EPEL libort is used by:
> 
> [paul at thinkpad ~]$ repoquery -qa --whatrequires libotr
> bitlbee-otr-0:3.0.4-3.fc17.x86_64
> bitlbee-otr-0:3.0.5-1.fc17.x86_64
> climm-0:0.7.1-4.fc17.x86_64
> irssi-otr-0:0.3-5.fc17.x86_64
> kdenetwork-kopete-7:4.8.3-1.fc17.x86_64
> kdenetwork-kopete-7:4.8.5-1.fc17.x86_64
> kdenetwork-kopete-libs-7:4.8.3-1.fc17.i686
> kdenetwork-kopete-libs-7:4.8.3-1.fc17.x86_64
> kdenetwork-kopete-libs-7:4.8.5-1.fc17.i686
> kdenetwork-kopete-libs-7:4.8.5-1.fc17.x86_64
> libotr-devel-0:3.2.1-1.fc17.i686
> libotr-devel-0:3.2.1-1.fc17.x86_64
> mcabber-0:0.10.1-3.fc17.x86_64
> pidgin-otr-0:3.2.1-1.fc17.x86_64
> xchat-otr-0:0.3-5.fc17.x86_64
> 
> So 7 clients use it, so I am not going to assume all of these can fix
> their code within a few days.

Indeed not.  They can continue to depend on the old version of libotr.
(Your libotr3 package, if I understand it?  But does that mean you have
to change all of the above packages to explicitly name libotr3?  If I
understand the Debian/Ubuntu method correctly, the package name has been
libotr2 all along, and all those other programs name libotr2 as their
dependency.  The new package will be libotr5, and programs that update
their use of libotr can then switch their dependency to libotr5.)

> >>Do the old libotr and the new interoperate?  Specifically, if one person
> >>is running the current pidgin-otr/libotr, and another both new ones, can
> >>they still talk?
> >
> >Yes.  The new one will just fall back to the old protocol when speaking
> >to old clients.
> 
> Just to clarify (and confirm I'm right), the above listed software
> cannot just use libotr-4. They need to be fixed for libotr-4. However,
> code fixed to use libotr-4, can talk to clients based on libotr-3 and
> libotr-4.

That is correct.  (And to clients based on any of the independent
implementations of the OTRv3 protocol in languages like Scheme, Python,
Javascript, etc.)

   - Ian