[gentoo-commits] repo/gentoo:master commit in: x11-plugins/pidgin-gnome-keyring/files/, x11-plugins/pidgin-gnome-keyring/

public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed

From: "Sam Jorna" <wraeth@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: x11-plugins/pidgin-gnome-keyring/files/, x11-plugins/pidgin-gnome-keyring/
Date: Thu, 28 Apr 2016 15:15:24 +0000 (UTC)	[thread overview]
Message-ID: <1461856492.5f5f50e4655d7da1cedc0f9c49a8d20010f9a6f1.wraeth@gentoo> (raw)

commit:     5f5f50e4655d7da1cedc0f9c49a8d20010f9a6f1
Author:     Marek Szuba <Marek.Szuba <AT> cern <DOT> ch>
AuthorDate: Thu Apr 28 08:06:38 2016 +0000
Commit:     Sam Jorna <wraeth <AT> gentoo <DOT> org>
CommitDate: Thu Apr 28 15:14:52 2016 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5f5f50e4

x11-plugins/pidgin-gnome-keyring: new ebuild, initial version 2.0

By default Pidgin/Purple store saved passwords in plain text in their
configuration files. This plug-in makes it possible to store passwords
in a keyring instead.

Gentoo-Bug: 581422
Package-Manager: portage-2.2.28
Closes: https://github.com/gentoo/gentoo/pull/1368

 x11-plugins/pidgin-gnome-keyring/Manifest          |  1 +
 .../files/pidgin-gnome-keyring-2.0-plugindir.patch | 21 ++++++++++++
 x11-plugins/pidgin-gnome-keyring/metadata.xml      | 18 ++++++++++
 .../pidgin-gnome-keyring-2.0.ebuild                | 38 ++++++++++++++++++++++
 4 files changed, 78 insertions(+)

diff --git a/x11-plugins/pidgin-gnome-keyring/Manifest b/x11-plugins/pidgin-gnome-keyring/Manifest
new file mode 100644
index 0000000..ea47716
--- /dev/null
+++ b/x11-plugins/pidgin-gnome-keyring/Manifest
@@ -0,0 +1 @@
+DIST pidgin-gnome-keyring-2.0.tar.gz 12066 SHA256 f75bc1a859226a5ad7cf3012925835a4d70b83dcac57a95d452194601b03191c SHA512 b1f83c107631a7105aa517312f13d745922b8033afc15069cba1c515caeee9e6ad89c4c7a5f96c561713d7f7a6ca3f03cff8fb11566a8ea0d8980f10e85d4610 WHIRLPOOL 84549c2240121400c46be51e4562df1db27cd900e6170aabab9d18761b93af1b5b1b60dac4ea7124cadf22325e6b79efcae569573edb36458c2d8fe673962d23

diff --git a/x11-plugins/pidgin-gnome-keyring/files/pidgin-gnome-keyring-2.0-plugindir.patch b/x11-plugins/pidgin-gnome-keyring/files/pidgin-gnome-keyring-2.0-plugindir.patch
new file mode 100644
index 0000000..6aa6ffc
--- /dev/null
+++ b/x11-plugins/pidgin-gnome-keyring/files/pidgin-gnome-keyring-2.0-plugindir.patch
@@ -0,0 +1,21 @@
+--- a/Makefile	2015-02-07 03:23:05.000000000 +0000
++++ b/Makefile	2016-04-28 09:53:59.915565380 +0000
+@@ -2,6 +2,7 @@
+ 
+ SECRETFLAGS = `pkg-config --libs --cflags libsecret-1`
+ PURPLEFLAGS = `pkg-config --cflags purple`
++PLUGINDIR = `pkg-config --variable=plugindir purple`
+ VERSION = $(shell cat VERSION)
+ ifeq ($(strip $(VERSION)),)
+ 	VERSION = `git describe --tags`
+@@ -18,8 +19,8 @@
+ 	${CC} ${CFLAGS} ${LDFLAGS} -Wall -I. -g -O2 ${TARGET}.c -o ${TARGET}.so -shared -fPIC -DPIC -ggdb ${PURPLEFLAGS} ${SECRETFLAGS} -DVERSION=\"${VERSION}\"
+ 
+ install: ${TARGET}.so
+-	mkdir -p ${DESTDIR}/usr/lib/purple-2/
+-	cp ${TARGET}.so ${DESTDIR}/usr/lib/purple-2/
++	mkdir -p ${DESTDIR}/$(PLUGINDIR)/
++	cp ${TARGET}.so ${DESTDIR}/$(PLUGINDIR)/
+ 
+ install_local: ${TARGET}.so
+ 	mkdir -p ~/.purple/plugins

diff --git a/x11-plugins/pidgin-gnome-keyring/metadata.xml b/x11-plugins/pidgin-gnome-keyring/metadata.xml
new file mode 100644
index 0000000..cb327e2
--- /dev/null
+++ b/x11-plugins/pidgin-gnome-keyring/metadata.xml
@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
+<pkgmetadata>
+	<maintainer type="person">
+		<email>Marek.Szuba@cern.ch</email>
+		<name>Marek Szuba</name>
+	</maintainer>
+	<maintainer type="project">
+		<email>proxy-maint@gentoo.org</email>
+		<name>Gentoo Proxy Maintainers Project</name>
+	</maintainer>
+	<longdescription lang="en">
+	Pidgin usually stores passwords as plaintext with the "save password"
+	function. This plugin instead saves all passwords to the system
+	keyring, which some would argue is a more secure form of password
+	storage.
+	</longdescription>
+</pkgmetadata>

diff --git a/x11-plugins/pidgin-gnome-keyring/pidgin-gnome-keyring-2.0.ebuild b/x11-plugins/pidgin-gnome-keyring/pidgin-gnome-keyring-2.0.ebuild
new file mode 100644
index 0000000..99560c3
--- /dev/null
+++ b/x11-plugins/pidgin-gnome-keyring/pidgin-gnome-keyring-2.0.ebuild
@@ -0,0 +1,38 @@
+# Copyright 1999-2016 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+# $Id$
+
+EAPI=6
+
+DESCRIPTION="Integrates Pidgin (and libpurple) with the system keyring"
+HOMEPAGE="https://github.com/aebrahim/pidgin-gnome-keyring"
+SRC_URI="https://github.com/aebrahim/${PN}/archive/${PV}.tar.gz -> ${P}.tar.gz"
+
+LICENSE="GPL-2+"
+SLOT="0"
+KEYWORDS="~amd64 ~x86"
+
+RDEPEND="app-crypt/libsecret
+	net-im/pidgin"
+DEPEND="${RDEPEND}
+	virtual/pkgconfig"
+
+PATCHES=(
+	"${FILESDIR}/${P}-plugindir.patch"
+)
+
+src_prepare() {
+	default
+
+	# This file is used by the upstream Makefile yet is missing from at least
+	# some release tarballs.
+	if [ ! -f VERSION ]; then
+		echo "${PV}" > VERSION || die "failed to recreate VERSION file"
+	fi
+
+	sed -i \
+		-e 's|-O2||g' \
+		-e 's|-ggdb||g' \
+		-e 's|-g||g' \
+		Makefile || die "stripping hard-coded flags failed"
+}

next             reply	other threads:[~2016-04-28 15:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-28 15:15 Sam Jorna [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-05-26  9:09 [gentoo-commits] repo/gentoo:master commit in: x11-plugins/pidgin-gnome-keyring/files/, x11-plugins/pidgin-gnome-keyring/ Marek Szuba

find likely ancestor, descendant, or conflicting patches for this message:
( dfblob:ea47716 dfblob:6aa6ffc dfblob:cb327e2 dfblob:99560c3 )
 OR (
bs:"[gentoo-commits] repo/gentoo:master commit in: x11-plugins/pidgin-gnome-keyring/files/, x11-plugins/pidgin-gnome-keyring/" )
	(help)

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=1461856492.5f5f50e4655d7da1cedc0f9c49a8d20010f9a6f1.wraeth@gentoo \
    --to=wraeth@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