Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Update libotr to version 4.0.0 #14731

Closed
wants to merge 1 commit into from

6 participants

@marvinone

I've done two things:
1. added a version string to the old libotr-version (3.2.0)
2. updated the libotr-Formula to version 4.0.0

I don't know if the first step is senseless - but i think it won't break anything and so it's more consistent.

Only tested on my Mountain-Lion iMac here. Installs like a charm.

@jacknagel
Owner

Homebrew can read simple version strings from the URL, so both of these are redundant; remove the, and squash to a single commit. Thanks!

@marvinone

Allright, now it's like requested: No version-string and only one commit.

@jacknagel
Owner

Looks like this breaks mcabber; at least, it chokes at configure.

@marvinone

Jeah, seams mcabber is not ready for libotr v4:

checking for libotr CFLAGS... 
checking for libotr LIBS...  -lotr
checking for libotr headers version 3.x >= 3.1.0... not present.
checking for otrl_message_receiving in -lotr... yes
configure: error: libotr 3.1.0 or newer is required.
Error: #<BuildError: Failed executing: ./configure --disable-debug --disable-dependency-tracking --prefix=/usr/loca/Cellar/mcabber/0.10.1 --enable-otr>

libotr v4 was released two days ago, so most of the software have to be updated to the new version.

On the Website there is a Upgrade-Readme which tells us:

Note that applications compiled against previous versions of OTR will not work with libotr 4.0.0.

What's the common approach in such a case? libotr4 ?

@nkoehring

ArchLinux have a libotr3 package which is installed to /usr/include/libotr3/ and /usr/lib/libotr3.so. Maybe that helps some people as a quick fix.

@adamv
Owner

MacPorts is still only packaging 3.x; do we need to keep an otr 3 in core?

@jacknagel
Owner

The stuff in Homebrew that depends on this is either unmaintained or rarely updated, and does not work against 4.x

@adamv
Owner

We can't let that stuff prevent adoption of 4.x if that is the right thing to do.

@jacknagel
Owner

Yeah that was mostly just fyi

@jacknagel
Owner

I'd be willing to eject those things from core, actually.

@adamv
Owner
$ brew uses libotr
mcabber

Yeah I don't use either of these.

@adamv
Owner

MCABBER has recent updates, though, so presumably they would be receptive to 4.x compatibility if it wasn't hard to do.

@mikemcquaid
Owner

Shall we bin both of these from core?

@adamv
Owner

Dunno, just posted a mcabber update.

@nonamed108

Any update on this?

@adamv
Owner

Won't happen unless someone sorts out macabber compatibility.

@nonamed108

Gotcha. Worthwhile to update the formula to at least pull the latest 3.2.x? Looks like 3.2.1 addresses a couple of security issues.

@adamv
Owner

Sure.

@adamv
Owner

Added to Homebrew-versions: Homebrew/homebrew-versions@37e621e

@adamv adamv closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Commits on Sep 5, 2012
  1. @marvinone

    libotr.rb: Updated from v3.2.0 to v4.0.0

    marvinone authored vamn committed
This page is out of date. Refresh to see the latest.
Showing with 2 additions and 2 deletions.
  1. +2 −2 Library/Formula/libotr.rb
View
4 Library/Formula/libotr.rb
@@ -1,9 +1,9 @@
require 'formula'
class Libotr < Formula
- url 'http://www.cypherpunks.ca/otr/libotr-3.2.0.tar.gz'
homepage 'http://www.cypherpunks.ca/otr/'
- sha1 'e5e10b8ddaf59b0ada6046d156d0431cd2790db9'
+ url 'http://www.cypherpunks.ca/otr/libotr-4.0.0.tar.gz'
+ sha1 '8865e9011b8674290837afcf7caf90c492ae09cc'
depends_on 'libgcrypt'
Something went wrong with that request. Please try again.