public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Daniel Black (dragonheart)" <dragonheart@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in net-libs/libzrtpcpp: ChangeLog libzrtpcpp-1.4.1.ebuild libzrtpcpp-1.1.0.ebuild
Date: Tue, 27 Jan 2009 17:54:38 +0000	[thread overview]
Message-ID: <E1LRs90-00086o-NN@stork.gentoo.org> (raw)

dragonheart    09/01/27 17:54:38

  Modified:             ChangeLog
  Added:                libzrtpcpp-1.4.1.ebuild
  Removed:              libzrtpcpp-1.1.0.ebuild
  Log:
  version bump
  (Portage version: 2.2_rc20/cvs/Linux 2.6.26-gentoo-r4 x86_64)

Revision  Changes    Path
1.11                 net-libs/libzrtpcpp/ChangeLog

file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/net-libs/libzrtpcpp/ChangeLog?rev=1.11&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/net-libs/libzrtpcpp/ChangeLog?rev=1.11&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo-x86/net-libs/libzrtpcpp/ChangeLog?r1=1.10&r2=1.11

Index: ChangeLog
===================================================================
RCS file: /var/cvsroot/gentoo-x86/net-libs/libzrtpcpp/ChangeLog,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- ChangeLog	19 Jun 2008 11:17:55 -0000	1.10
+++ ChangeLog	27 Jan 2009 17:54:38 -0000	1.11
@@ -1,6 +1,12 @@
 # ChangeLog for net-libs/libzrtpcpp
-# Copyright 1999-2008 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/net-libs/libzrtpcpp/ChangeLog,v 1.10 2008/06/19 11:17:55 dragonheart Exp $
+# Copyright 1999-2009 Gentoo Foundation; Distributed under the GPL v2
+# $Header: /var/cvsroot/gentoo-x86/net-libs/libzrtpcpp/ChangeLog,v 1.11 2009/01/27 17:54:38 dragonheart Exp $
+
+*libzrtpcpp-1.4.1 (27 Jan 2009)
+
+  27 Jan 2009; Daniel Black <dragonheart@gentoo.org>
+  -libzrtpcpp-1.1.0.ebuild, +libzrtpcpp-1.4.1.ebuild:
+  version bump
 
 *libzrtpcpp-1.3.0 (19 Jun 2008)
 



1.1                  net-libs/libzrtpcpp/libzrtpcpp-1.4.1.ebuild

file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/net-libs/libzrtpcpp/libzrtpcpp-1.4.1.ebuild?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/net-libs/libzrtpcpp/libzrtpcpp-1.4.1.ebuild?rev=1.1&content-type=text/plain

Index: libzrtpcpp-1.4.1.ebuild
===================================================================
# Copyright 1999-2009 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: /var/cvsroot/gentoo-x86/net-libs/libzrtpcpp/libzrtpcpp-1.4.1.ebuild,v 1.1 2009/01/27 17:54:38 dragonheart Exp $

DESCRIPTION="GNU RTP stack for the zrtp protocol specification developed by Phil Zimmermen"
HOMEPAGE="http://www.gnutelephony.org/index.php/GNU_ZRTP"
SRC_URI="mirror://gnu/ccrtp/${P}.tar.gz"
KEYWORDS="~amd64 ~ppc ~ppc64 ~x86"
LICENSE="GPL-2"
IUSE=""
SLOT="0"

RDEPEND=">=net-libs/ccrtp-1.5.0
	>=dev-cpp/commoncpp2-1.5.1
	|| ( dev-libs/libgcrypt
		>=dev-libs/openssl-0.9.8 )"
DEPEND="${RDEPEND}
	>=dev-util/pkgconfig-0.9.0"

src_install() {
	emake DESTDIR="${D}" install || die
	dodoc README AUTHORS
}






                 reply	other threads:[~2009-01-27 17:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1LRs90-00086o-NN@stork.gentoo.org \
    --to=dragonheart@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox