Conversation
Homebrew can read simple version strings from the URL, so both of these are redundant; remove the, and squash to a single commit. Thanks! |
Allright, now it's like requested: No version-string and only one commit. |
Looks like this breaks mcabber; at least, it chokes at configure. |
Jeah, seams mcabber is not ready for libotr v4:
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:
What's the common approach in such a case? libotr4 ? |
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. |
MacPorts is still only packaging 3.x; do we need to keep an otr 3 in core? |
The stuff in Homebrew that depends on this is either unmaintained or rarely updated, and does not work against 4.x |
We can't let that stuff prevent adoption of 4.x if that is the right thing to do. |
Yeah that was mostly just fyi |
I'd be willing to eject those things from core, actually. |
Yeah I don't use either of these. |
MCABBER has recent updates, though, so presumably they would be receptive to 4.x compatibility if it wasn't hard to do. |
Shall we bin both of these from core? |
Dunno, just posted a mcabber update. |
Any update on this? |
Won't happen unless someone sorts out macabber compatibility. |
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. |
Sure. |
Added to Homebrew-versions: https://github.com/Homebrew/homebrew-versions/commit/37e621e238141451dd30dc17b7f999cab435105b |
I've done two things:
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.