248161ffeb
According to their few additional commit logs, it's worth it. I also set libotr to use the latest libgcrypt, related to a comment in libotr commit. They talk about a libgcrypt fix that will have more chances to be in the latest libgcrypt.
22 lines
571 B
Nix
22 lines
571 B
Nix
{stdenv, fetchgit, libgcrypt, autoconf, automake, libtool}:
|
|
|
|
stdenv.mkDerivation rec {
|
|
name = "libotr-20130821-git-f0f8a2";
|
|
src = fetchgit {
|
|
url = "http://git.code.sf.net/p/otr/libotr";
|
|
rev = "f0f8a2";
|
|
sha256 = "08019r8bnk8f4yx6574jdz217p283ry7dmpqcad2d87yhkdmc3mm";
|
|
};
|
|
|
|
NIX_LDFLAGS = "-lssp";
|
|
|
|
propagatedBuildInputs = [ libgcrypt autoconf automake libtool ];
|
|
|
|
preConfigure = "autoreconf -vfi";
|
|
|
|
meta = {
|
|
homepage = "http://www.cypherpunks.ca/otr/";
|
|
license = "LGPLv2.1";
|
|
description = "Library for Off-The-Record Messaging";
|
|
};
|
|
}
|