From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-arch/sharutils/
Date: Sat, 2 May 2020 12:18:59 +0000 (UTC) [thread overview]
Message-ID: <1588421933.b58b000f7c7f792561bdf7b160d9be5711a0462c.slyfox@gentoo> (raw)
commit: b58b000f7c7f792561bdf7b160d9be5711a0462c
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Sat May 2 12:18:35 2020 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Sat May 2 12:18:53 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b58b000f
app-arch/sharutils: bump up to EAPI=7
Package-Manager: Portage-2.3.99, Repoman-2.3.22
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>
app-arch/sharutils/sharutils-4.15.2-r2.ebuild | 41 +++++++++++++++++++++++++++
1 file changed, 41 insertions(+)
diff --git a/app-arch/sharutils/sharutils-4.15.2-r2.ebuild b/app-arch/sharutils/sharutils-4.15.2-r2.ebuild
new file mode 100644
index 00000000000..2aaa0c101de
--- /dev/null
+++ b/app-arch/sharutils/sharutils-4.15.2-r2.ebuild
@@ -0,0 +1,41 @@
+# Copyright 1999-2020 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI="7"
+
+inherit eutils flag-o-matic
+
+MY_P="${P/_/-}"
+DESCRIPTION="Tools to deal with shar archives"
+HOMEPAGE="https://www.gnu.org/software/sharutils/"
+SRC_URI="mirror://gnu/${PN}/${P}.tar.xz"
+
+LICENSE="GPL-3"
+SLOT="0"
+KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~m68k ~mips ~ppc ~ppc64 ~s390 ~sparc ~x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~sparc-solaris ~x64-solaris ~x86-solaris"
+IUSE="nls"
+
+DEPEND="app-arch/xz-utils
+ sys-apps/texinfo
+ nls? ( >=sys-devel/gettext-0.10.35 )"
+
+S=${WORKDIR}/${MY_P}
+
+PATCHES=(
+ "${FILESDIR}"/${PN}-4.15.2-glibc228.patch
+ "${FILESDIR}"/${PN}-4.15.2-CVE-2018-1000097.patch
+ "${FILESDIR}"/${PN}-4.15.2-gcc-10.patch
+)
+
+src_prepare() {
+ default
+
+ # Upstream is aware but thinks this isn't a bug/problem in sharutils itself
+ # See http://lists.gnu.org/archive/html/bug-gnu-utils/2013-10/msg00011.html
+ append-cflags $(test-flags-CC -Wno-error=format-security)
+}
+
+src_configure() {
+ strip-linguas -u po
+ econf $(use_enable nls)
+}
next reply other threads:[~2020-05-02 12:19 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-02 12:18 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-26 6:33 [gentoo-commits] repo/gentoo:master commit in: app-arch/sharutils/ Sam James
2024-03-27 4:52 Sam James
2022-08-22 17:33 WANG Xuerui
2021-06-30 10:15 Ulrich Müller
2021-05-01 23:02 David Seifert
2021-04-26 10:38 Sam James
2021-04-26 10:34 Sam James
2021-04-25 15:56 Sam James
2021-04-25 15:52 Sam James
2021-04-25 15:21 Sam James
2021-04-25 12:32 Sam James
2021-04-25 12:32 Sam James
2021-04-21 19:02 Sam James
2021-04-21 19:02 Sam James
2021-01-06 12:52 Fabian Groffen
2019-08-10 16:32 Aaron Bauman
2019-05-02 15:31 Matt Turner
2019-05-01 6:22 Matt Turner
2019-05-01 6:22 Matt Turner
2019-04-27 20:50 Sergei Trofimovich
2019-04-10 14:45 Aaron Bauman
2019-04-08 6:05 Matt Turner
2019-04-08 2:18 Thomas Deutschmann
2019-04-02 12:08 Mikle Kolyada
2019-04-02 12:08 Mikle Kolyada
2019-03-24 17:00 Mikle Kolyada
2019-03-16 14:01 Mikle Kolyada
2019-03-15 10:00 Mikle Kolyada
2019-03-14 19:41 Sergei Trofimovich
2017-09-17 2:18 Thomas Deutschmann
2017-07-17 12:54 Fabian Groffen
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=1588421933.b58b000f7c7f792561bdf7b160d9be5711a0462c.slyfox@gentoo \
--to=slyfox@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