public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Yixun Lan" <dlan@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-vcs/git-publish/
Date: Fri, 19 Mar 2021 03:44:14 +0000 (UTC)	[thread overview]
Message-ID: <1616125287.300ca15b52e08471e02602f7422010f1e05d166a.dlan@gentoo> (raw)

commit:     300ca15b52e08471e02602f7422010f1e05d166a
Author:     Yixun Lan <dlan <AT> gentoo <DOT> org>
AuthorDate: Thu Mar 18 01:08:30 2021 +0000
Commit:     Yixun Lan <dlan <AT> gentoo <DOT> org>
CommitDate: Fri Mar 19 03:41:27 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=300ca15b

dev-vcs/git-publish: add version 1.7.0

git-pushlish make it easy to send patches

Package-Manager: Portage-3.0.17, Repoman-3.0.2
Signed-off-by: Yixun Lan <dlan <AT> gentoo.org>

 dev-vcs/git-publish/Manifest                 |  1 +
 dev-vcs/git-publish/git-publish-1.7.0.ebuild | 43 ++++++++++++++++++++++++++++
 dev-vcs/git-publish/metadata.xml             | 17 +++++++++++
 3 files changed, 61 insertions(+)

diff --git a/dev-vcs/git-publish/Manifest b/dev-vcs/git-publish/Manifest
new file mode 100644
index 00000000000..09e46d1b96d
--- /dev/null
+++ b/dev-vcs/git-publish/Manifest
@@ -0,0 +1 @@
+DIST git-publish-1.7.0.tar.gz 21569 BLAKE2B 1438e5018ebe7d258fee2527597e56080b574765a87b03d814b6d0d41c68397cba6099866382e9f2c560d8bab58214fb9e5f54f0127433917178337df81ff789 SHA512 dbf343e0284c52edd42ba8d844a9db90810ddd02e7a98bcd1c2af72cd9f5242e9c0a9ea921edf47583bfe05943288286e57a018a7a6b2dcf25bae4f663225025

diff --git a/dev-vcs/git-publish/git-publish-1.7.0.ebuild b/dev-vcs/git-publish/git-publish-1.7.0.ebuild
new file mode 100644
index 00000000000..7a000d78110
--- /dev/null
+++ b/dev-vcs/git-publish/git-publish-1.7.0.ebuild
@@ -0,0 +1,43 @@
+# Copyright 2021 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=7
+
+PYTHON_COMPAT=( python3_{8..9} )
+inherit python-single-r1
+
+DESCRIPTION="Tool for preparing and storing patch revisions as git tag"
+HOMEPAGE="https://github.com/stefanha/git-publish"
+SRC_URI="https://github.com/stefanha/git-publish/archive/v${PV}.tar.gz -> ${P}.tar.gz"
+
+LICENSE="MIT"
+SLOT="0"
+KEYWORDS="~amd64"
+IUSE="+man"
+REQUIRED_USE="${PYTHON_REQUIRED_USE}"
+
+RDEPEND="${PYTHON_DEPS}
+	dev-vcs/git
+"
+BDEPEND="${PYTHON_DEPS}
+	man? ( dev-lang/perl )
+"
+
+src_prepare() {
+	default
+	python_fix_shebang git-publish
+}
+
+src_compile() {
+	if use man; then
+		pod2man --center "git-publish Documentation" --release "${PV}" \
+			git-publish.pod git-publish.1 || die
+	fi
+}
+
+src_install() {
+	dobin git-publish
+	use man && doman git-publish.1
+	insinto /usr/share/${PN}/hooks
+	doins hooks/pre-publish-send-email.example
+}

diff --git a/dev-vcs/git-publish/metadata.xml b/dev-vcs/git-publish/metadata.xml
new file mode 100644
index 00000000000..b97d2e99f3b
--- /dev/null
+++ b/dev-vcs/git-publish/metadata.xml
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
+<pkgmetadata>
+	<longdescription>
+		git-publish prepares patches and stores them as git tags for future reference.
+		It works with individual patches as well as patch series. Revision numbering
+		is handled automatically.
+	</longdescription>
+	<maintainer type="person">
+		<email>dlan@gentoo.org</email>
+		<name>Yixun Lan</name>
+	</maintainer>
+	<stabilize-allarches/>
+	<upstream>
+		<remote-id type="github">stefanha/git-publish</remote-id>
+	</upstream>
+</pkgmetadata>


             reply	other threads:[~2021-03-19  3:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-19  3:44 Yixun Lan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-04-26  8:46 [gentoo-commits] repo/gentoo:master commit in: dev-vcs/git-publish/ Yixun Lan
2022-05-14 12:55 Yixun Lan
2022-05-14 12:55 Yixun Lan
2024-02-11  8:28 Yixun Lan
2024-02-11  8:28 Yixun Lan

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=1616125287.300ca15b52e08471e02602f7422010f1e05d166a.dlan@gentoo \
    --to=dlan@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