From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-portage/gverify/
Date: Wed, 1 Aug 2018 20:53:32 +0000 (UTC) [thread overview]
Message-ID: <1533156804.b640e0eb72b4cf87be93d2a8c97d34534fbcfafa.mgorny@gentoo> (raw)
commit: b640e0eb72b4cf87be93d2a8c97d34534fbcfafa
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Wed Aug 1 20:53:00 2018 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Wed Aug 1 20:53:24 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b640e0eb
app-portage/gverify: New package for gentoo.git verification tool
app-portage/gverify/Manifest | 1 +
app-portage/gverify/gverify-1.ebuild | 30 ++++++++++++++++++++++++++++++
app-portage/gverify/metadata.xml | 8 ++++++++
3 files changed, 39 insertions(+)
diff --git a/app-portage/gverify/Manifest b/app-portage/gverify/Manifest
new file mode 100644
index 00000000000..7534034172c
--- /dev/null
+++ b/app-portage/gverify/Manifest
@@ -0,0 +1 @@
+DIST gverify-1.tar.gz 4558 BLAKE2B 193fb63dd3816b4577314199e4f8606a20f60d883f22f36636f1dba4c3fe4a701e89fd352b33ee3ce5bfb10b39e351f971aa55c8cd6eef493fc492e2c4c5d17e SHA512 f666306973bf173683edd845499ea1b244ffc9254ed0d816660022f871e7cec480d452fd962db5417b23d3101496b80a49caece29cbddf3058e2a21ec945a268
diff --git a/app-portage/gverify/gverify-1.ebuild b/app-portage/gverify/gverify-1.ebuild
new file mode 100644
index 00000000000..3564e46d305
--- /dev/null
+++ b/app-portage/gverify/gverify-1.ebuild
@@ -0,0 +1,30 @@
+# Copyright 1999-2018 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=7
+
+PYTHON_COMPAT=( python{2_7,3_{4,5,6,7}} )
+inherit python-single-r1
+
+DESCRIPTION="gentoo.git signature verification tool"
+HOMEPAGE="https://github.com/mgorny/gverify"
+SRC_URI="https://github.com/mgorny/gverify/archive/v${PV}.tar.gz -> ${P}.tar.gz"
+
+LICENSE="BSD-2"
+SLOT="0"
+KEYWORDS="~amd64 ~x86"
+IUSE=""
+
+RDEPEND="${PYTHON_DEPS}
+ app-crypt/gnupg
+ dev-vcs/git"
+DEPEND="${PYTHON_DEPS}"
+
+src_compile() {
+ emake PREFIX="${EPREFIX}"/usr
+}
+
+src_install() {
+ emake install DESTDIR="${D}" PREFIX=/usr
+ dodoc README
+}
diff --git a/app-portage/gverify/metadata.xml b/app-portage/gverify/metadata.xml
new file mode 100644
index 00000000000..0319eec4c8b
--- /dev/null
+++ b/app-portage/gverify/metadata.xml
@@ -0,0 +1,8 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
+<pkgmetadata>
+ <maintainer type="person">
+ <email>mgorny@gentoo.org</email>
+ <name>Michał Górny</name>
+ </maintainer>
+</pkgmetadata>
next reply other threads:[~2018-08-01 20:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-01 20:53 Michał Górny [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-07-25 14:30 [gentoo-commits] repo/gentoo:master commit in: app-portage/gverify/ Michał Górny
2019-10-30 16:36 Michał Górny
2019-12-08 10:23 Michał Górny
2019-12-08 10:23 Michał Górny
2020-02-10 11:54 Michał Górny
2021-04-20 7:02 Michał Górny
2021-12-16 1:43 Craig Andrews
2022-07-31 16:08 Jakov Smolić
2022-08-08 19:59 Jakov Smolić
2022-08-10 14:20 Michał Górny
2023-04-08 13:40 Michał Górny
2023-04-08 13:40 Michał Górny
2024-03-03 16:20 Michał Górny
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=1533156804.b640e0eb72b4cf87be93d2a8c97d34534fbcfafa.mgorny@gentoo \
--to=mgorny@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