public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Pacho Ramos" <pacho@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-crypt/seahorse/
Date: Sat, 14 Nov 2015 15:27:46 +0000 (UTC)	[thread overview]
Message-ID: <1447514822.3be93331162a0fb44432ac55572431901300dbbb.pacho@gentoo> (raw)

commit:     3be93331162a0fb44432ac55572431901300dbbb
Author:     Pacho Ramos <pacho <AT> gentoo <DOT> org>
AuthorDate: Sat Nov 14 14:57:53 2015 +0000
Commit:     Pacho Ramos <pacho <AT> gentoo <DOT> org>
CommitDate: Sat Nov 14 15:27:02 2015 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3be93331

app-crypt/seahorse: Version bump

Package-Manager: portage-2.2.24

 app-crypt/seahorse/Manifest               |  1 +
 app-crypt/seahorse/seahorse-3.18.0.ebuild | 67 +++++++++++++++++++++++++++++++
 2 files changed, 68 insertions(+)

diff --git a/app-crypt/seahorse/Manifest b/app-crypt/seahorse/Manifest
index d6f5147..ed73677 100644
--- a/app-crypt/seahorse/Manifest
+++ b/app-crypt/seahorse/Manifest
@@ -1,2 +1,3 @@
 DIST seahorse-3.14.1.tar.xz 1504128 SHA256 092a890982fa594da8a384f156b961392f69ce5d9518a9801035e6deb1f05e93 SHA512 1147ea601c1cb17dd1606d02f86261b0381dfdab14329fee7d68bd635420fec98174b2509b09c68216918bd9ca31f22ea538fa34cae1a8e0f4c44714b9693c0f WHIRLPOOL 208c841a28b8c7c0916c02e1a68eaa7c74681c5a3b8e0be30f65a4da953cefd9bb94d57373640513b68de9b204e9d1fc65429bf5dca0344336390068fe4a47e1
 DIST seahorse-3.16.0.tar.xz 1496188 SHA256 770a5f03b8745054ef04cef9923dd713b1fbf309169150bc8dd32d7e5f7ee131 SHA512 54e020e907c0053762bf78fd1b4a47ed30d253a89d9063f6daa33598fc3cd97dca0af0cd66bb4a140223b6ae18db88a52bfc50f46987cb3a8d0351c115fba923 WHIRLPOOL 5e3c3ee17be55849c22019c7a9669380ae101e39d9c81e66d6140d500ef3882c2019f39491bfb37a9019c3fda78304aab9743dc3ae112646a4e9106493704372
+DIST seahorse-3.18.0.tar.xz 1555384 SHA256 530c889a01c4cad25df4c9ab58ab95d24747875789bc6116bef529d60fc1b667 SHA512 76475645d1f94a99bf12c3bbbd840526ab3f1da9c6dd7c8c7fca1cca1cdb22692c44d6107ed1f0192dacb6990c1bbc5c1e0bb9a412132fbf18b302d6059cb254 WHIRLPOOL a470024c7c187f854f7458de31ce8aae6f27ff99ee44d872c2298983391e3f39a2c22e5c201927a5b303ced1a614de9729af9625b59714b6cd580890714e5b79

diff --git a/app-crypt/seahorse/seahorse-3.18.0.ebuild b/app-crypt/seahorse/seahorse-3.18.0.ebuild
new file mode 100644
index 0000000..a916456
--- /dev/null
+++ b/app-crypt/seahorse/seahorse-3.18.0.ebuild
@@ -0,0 +1,67 @@
+# Copyright 1999-2015 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+# $Id$
+
+EAPI="5"
+GCONF_DEBUG="no"
+
+inherit gnome2
+
+DESCRIPTION="A GNOME application for managing encryption keys"
+HOMEPAGE="https://wiki.gnome.org/Apps/Seahorse"
+
+LICENSE="GPL-2+ FDL-1.1+"
+SLOT="0"
+IUSE="debug ldap zeroconf"
+KEYWORDS="~alpha ~amd64 ~arm ~ia64 ~ppc ~ppc64 ~sparc ~x86 ~x86-fbsd"
+
+COMMON_DEPEND="
+	>=app-crypt/gcr-3.11.91:=
+	>=dev-libs/glib-2.10:2
+	>=x11-libs/gtk+-3.4:3
+	>=app-crypt/libsecret-0.16
+	>=net-libs/libsoup-2.33.92:2.4
+	x11-misc/shared-mime-info
+
+	net-misc/openssh
+	>=app-crypt/gpgme-1
+	>=app-crypt/gnupg-2.0.12
+
+	ldap? ( net-nds/openldap:= )
+	zeroconf? ( >=net-dns/avahi-0.6:= )
+"
+DEPEND="${COMMON_DEPEND}
+	app-text/yelp-tools
+	dev-util/gdbus-codegen
+	>=dev-util/intltool-0.35
+	dev-util/itstool
+	sys-devel/gettext
+	virtual/pkgconfig
+"
+# Need seahorse-plugins git snapshot
+RDEPEND="${COMMON_DEPEND}
+	!<app-crypt/seahorse-plugins-2.91.0_pre20110114
+"
+
+src_prepare() {
+	# Do not mess with CFLAGS with USE="debug"
+	sed -e '/CFLAGS="$CFLAGS -g/d' \
+		-e '/CFLAGS="$CFLAGS -O0/d' \
+		-i configure.ac configure || die "sed 1 failed"
+
+	gnome2_src_prepare
+}
+
+src_configure() {
+	# bindir is needed due to bad macro expansion in desktop file, bug #508610
+	gnome2_src_configure \
+		--bindir=/usr/bin \
+		--enable-pgp \
+		--enable-ssh \
+		--enable-pkcs11 \
+		--enable-hkp \
+		$(use_enable debug) \
+		$(use_enable ldap) \
+		$(use_enable zeroconf sharing) \
+		VALAC=$(type -P true)
+}


             reply	other threads:[~2015-11-14 15:27 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-14 15:27 Pacho Ramos [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-11-14 15:27 [gentoo-commits] repo/gentoo:master commit in: app-crypt/seahorse/ Pacho Ramos
2016-06-24 20:06 Pacho Ramos
2017-08-09  6:59 Gilles Dartiguelongue
2017-10-07 17:32 Patrice Clement
2019-03-13 23:22 Mart Raudsepp
2019-03-14 10:47 Mart Raudsepp
2019-05-18 13:41 Mart Raudsepp
2019-08-04 15:05 Aaron Bauman
2019-09-22 20:28 Mart Raudsepp
2019-09-23  9:22 Mart Raudsepp
2019-12-08 20:27 Mart Raudsepp
2020-05-18  7:53 Mart Raudsepp
2020-07-17 20:44 Mart Raudsepp
2020-08-31 17:28 Mart Raudsepp
2020-12-11  3:24 Matt Turner
2021-02-26 19:02 Sam James
2021-03-07 22:19 Mart Raudsepp
2021-03-13  3:51 Matt Turner
2021-11-11 13:52 Pacho Ramos
2022-02-16 22:21 David Seifert
2022-04-17  6:30 Matt Turner
2022-04-17 18:11 Matt Turner
2022-05-21 21:00 Matt Turner
2022-10-01 17:16 Matt Turner
2022-10-29 22:33 Matt Turner
2023-03-01  6:10 Sam James
2023-07-27  8:29 WANG Xuerui
2024-06-03  7:56 Sam James
2024-11-28 15:16 Sam James
2025-01-16 16:55 Pacho Ramos
2025-01-16 16:55 Pacho Ramos

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=1447514822.3be93331162a0fb44432ac55572431901300dbbb.pacho@gentoo \
    --to=pacho@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