From: "Anthony G. Basile" <blueness@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-vpn/tinc/
Date: Sat, 21 Apr 2018 11:15:55 +0000 (UTC) [thread overview]
Message-ID: <1524309313.4b8c292c5c97cf34c3d8494b5d7d2195278c5340.blueness@gentoo> (raw)
commit: 4b8c292c5c97cf34c3d8494b5d7d2195278c5340
Author: Marty E. Plummer <hanetzer <AT> startmail <DOT> com>
AuthorDate: Fri Apr 20 16:47:35 2018 +0000
Commit: Anthony G. Basile <blueness <AT> gentoo <DOT> org>
CommitDate: Sat Apr 21 11:15:13 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4b8c292c
net-vpn/tinc: reworked UPSTREAM_VER to use eapply
Also dropped unneeded multilib eclass.
Package-Manager: Portage-2.3.31, Repoman-2.3.9
net-vpn/tinc/tinc-1.1_pre15.ebuild | 26 ++++++++++++--------------
1 file changed, 12 insertions(+), 14 deletions(-)
diff --git a/net-vpn/tinc/tinc-1.1_pre15.ebuild b/net-vpn/tinc/tinc-1.1_pre15.ebuild
index 57d5cee1828..ea6d0816b40 100644
--- a/net-vpn/tinc/tinc-1.1_pre15.ebuild
+++ b/net-vpn/tinc/tinc-1.1_pre15.ebuild
@@ -1,14 +1,14 @@
# Copyright 1999-2018 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
-EAPI="6"
+EAPI=6
MY_PV=${PV/_/}
MY_P=${PN}-${MY_PV}
PYTHON_COMPAT=( python2_7 )
-inherit autotools multilib python-single-r1 systemd
+inherit autotools python-single-r1 systemd
DESCRIPTION="tinc is an easy to configure VPN implementation"
HOMEPAGE="http://www.tinc-vpn.org/"
@@ -43,20 +43,18 @@ RDEPEND="${DEPEND}
vde? ( net-misc/vde )"
S="${WORKDIR}/${MY_P}"
-src_prepare() {
- # Upstream's patchset
- if [[ -n ${UPSTREAM_VER} ]]; then
- einfo "Try to apply Tinc Upstream patch set"
- EPATCH_SUFFIX="patch" \
- EPATCH_FORCE="yes" \
- EPATCH_OPTS="-p1" \
- epatch "${WORKDIR}"/patches-upstream
- fi
+# Upstream's patchset
+if [[ -n ${UPSTREAM_VER} ]]; then
+ PATCHES=( "${WORKDIR}"/patches-upstream )
+fi
- eapply "${FILESDIR}"/tinc-1.1-fix-paths.patch #560528
- eapply "${FILESDIR}"/${PN}-1.1-tinfo.patch #621868
- eapply_user
+PATCHES+=(
+ "${FILESDIR}"/${PN}-1.1-fix-paths.patch #560528
+ "${FILESDIR}"/${PN}-1.1-tinfo.patch #621868
+)
+src_prepare() {
+ default
eautoreconf
}
next reply other threads:[~2018-04-21 11:15 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-21 11:15 Anthony G. Basile [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-09 12:09 [gentoo-commits] repo/gentoo:master commit in: net-vpn/tinc/ Yixun Lan
2024-04-05 1:21 Sam James
2023-04-25 23:17 Sam James
2022-07-03 0:59 Sam James
2022-05-05 10:06 WANG Xuerui
2022-05-05 10:06 WANG Xuerui
2022-03-06 10:12 Jakov Smolić
2021-09-02 6:25 Yixun Lan
2021-06-28 23:25 Anthony G. Basile
2021-05-02 15:07 Mikle Kolyada
2021-01-06 15:06 Fabian Groffen
2020-02-24 14:58 Anthony G. Basile
2020-02-23 20:59 Anthony G. Basile
2019-08-27 14:34 Anthony G. Basile
2019-04-15 7:12 Yixun Lan
2019-04-15 7:12 Yixun Lan
2019-03-08 3:32 Yixun Lan
2019-03-08 3:32 Yixun Lan
2019-03-07 23:13 Anthony G. Basile
2018-10-10 1:24 Anthony G. Basile
2018-06-12 22:32 Anthony G. Basile
2018-06-12 22:26 Anthony G. Basile
2017-11-27 17:28 Pacho Ramos
2017-11-05 23:20 Anthony G. Basile
2017-09-02 22:24 Anthony G. Basile
2017-09-02 22:24 Anthony G. Basile
2017-09-02 22:24 Anthony G. Basile
2017-04-23 21:01 David Seifert
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=1524309313.4b8c292c5c97cf34c3d8494b5d7d2195278c5340.blueness@gentoo \
--to=blueness@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