Skip to content
This repository has been archived by the owner on Jul 4, 2023. It is now read-only.

Update libotr to version 4.0.0 #14731

Closed
wants to merge 1 commit into from
Closed

Update libotr to version 4.0.0 #14731

wants to merge 1 commit into from

Conversation

marvinone
Copy link

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
Copy link
Contributor

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
Copy link
Author

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

@jacknagel
Copy link
Contributor

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

@marvinone
Copy link
Author

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
Copy link

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
Copy link
Contributor

adamv commented Jan 7, 2013

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

@jacknagel
Copy link
Contributor

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

@adamv
Copy link
Contributor

adamv commented Jan 7, 2013

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

@jacknagel
Copy link
Contributor

Yeah that was mostly just fyi

@jacknagel
Copy link
Contributor

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

@adamv
Copy link
Contributor

adamv commented Jan 7, 2013

$ brew uses libotr
mcabber

Yeah I don't use either of these.

@adamv
Copy link
Contributor

adamv commented Jan 7, 2013

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

@MikeMcQuaid
Copy link
Member

Shall we bin both of these from core?

@adamv
Copy link
Contributor

adamv commented Feb 3, 2013

Dunno, just posted a mcabber update.

@ed-velez
Copy link
Contributor

Any update on this?

@adamv
Copy link
Contributor

adamv commented Apr 27, 2013

Won't happen unless someone sorts out macabber compatibility.

@ed-velez
Copy link
Contributor

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
Copy link
Contributor

adamv commented Apr 27, 2013

Sure.

@adamv
Copy link
Contributor

adamv commented Jun 9, 2013

@adamv adamv closed this Jun 9, 2013
@Homebrew Homebrew locked and limited conversation to collaborators Feb 16, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants