From: "David Seifert" <soap@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-devel/patch/
Date: Thu, 6 Jan 2022 09:07:33 +0000 (UTC) [thread overview]
Message-ID: <1641460034.ef511d7814808591e6a273ea1598dcc1b3a798cc.soap@gentoo> (raw)
commit: ef511d7814808591e6a273ea1598dcc1b3a798cc
Author: David Seifert <soap <AT> gentoo <DOT> org>
AuthorDate: Thu Jan 6 09:07:14 2022 +0000
Commit: David Seifert <soap <AT> gentoo <DOT> org>
CommitDate: Thu Jan 6 09:07:14 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ef511d78
sys-devel/patch: remove userland_BSD
Signed-off-by: David Seifert <soap <AT> gentoo.org>
sys-devel/patch/patch-2.7.6-r4.ebuild | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/sys-devel/patch/patch-2.7.6-r4.ebuild b/sys-devel/patch/patch-2.7.6-r4.ebuild
index 5919bbb39640..30d831025c06 100644
--- a/sys-devel/patch/patch-2.7.6-r4.ebuild
+++ b/sys-devel/patch/patch-2.7.6-r4.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2021 Gentoo Authors
+# Copyright 1999-2022 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI="7"
@@ -39,7 +39,6 @@ src_configure() {
local myeconfargs=(
$(use_enable xattr)
- --program-prefix="$(use userland_BSD && echo g)"
)
# Do not let $ED mess up the search for `ed` 470210.
ac_cv_path_ED=$(type -P ed) \
next reply other threads:[~2022-01-06 9:07 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 9:07 David Seifert [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-13 1:21 [gentoo-commits] repo/gentoo:master commit in: sys-devel/patch/ Sam James
2025-03-13 1:11 Sam James
2025-03-13 1:11 Sam James
2025-03-13 1:09 Sam James
2025-03-13 0:53 Sam James
2025-03-13 0:45 Sam James
2025-02-27 7:04 Eli Schwartz
2025-02-14 8:22 Eli Schwartz
2025-02-09 4:32 Sam James
2025-02-06 23:31 Eli Schwartz
2025-01-21 3:41 Sam James
2024-11-03 20:47 Eli Schwartz
2024-09-01 1:37 Sam James
2023-03-31 12:08 Arthur Zamarin
2023-02-24 18:36 Sam James
2023-01-29 0:59 Sam James
2023-01-27 8:05 Sam James
2023-01-27 8:05 Sam James
2023-01-27 8:05 Sam James
2023-01-27 8:05 Sam James
2023-01-27 6:31 Sam James
2023-01-27 6:31 Sam James
2022-10-30 15:51 Sam James
2022-04-07 3:57 Sam James
2021-01-06 15:32 Fabian Groffen
2020-12-27 18:18 Fabian Groffen
2020-05-04 17:36 Thomas Deutschmann
2019-08-23 10:26 Mikle Kolyada
2019-08-23 10:26 Mikle Kolyada
2019-08-23 10:26 Mikle Kolyada
2019-08-23 10:26 Mikle Kolyada
2019-08-23 10:26 Mikle Kolyada
2019-08-23 10:00 Agostino Sarubbo
2019-08-19 6:57 Sergei Trofimovich
2019-08-18 10:12 Sergei Trofimovich
2019-08-18 10:10 Sergei Trofimovich
2019-08-18 10:08 Sergei Trofimovich
2019-08-18 8:29 Sergei Trofimovich
2019-08-16 22:38 Thomas Deutschmann
2019-08-16 21:53 Aaron Bauman
2019-08-16 21:50 Mikle Kolyada
2019-05-03 23:38 Mikle Kolyada
2019-04-11 9:49 Mikle Kolyada
2019-04-11 9:49 Mikle Kolyada
2019-04-11 9:49 Mikle Kolyada
2019-04-10 22:03 Sergei Trofimovich
2019-04-08 8:39 Mart Raudsepp
2019-04-08 6:42 Mikle Kolyada
2019-04-07 21:53 Mikle Kolyada
2019-04-07 21:41 Mikle Kolyada
2019-04-07 20:52 Sergei Trofimovich
2019-04-05 20:47 Agostino Sarubbo
2018-08-31 3:26 Thomas Deutschmann
2018-08-31 3:26 Thomas Deutschmann
2018-05-27 14:53 Mikle Kolyada
2018-04-24 15:14 Mart Raudsepp
2018-03-22 16:37 Mikle Kolyada
2018-03-18 1:02 Matt Turner
2018-03-18 1:02 Matt Turner
2018-03-15 14:14 Mikle Kolyada
2018-03-05 13:57 Tobias Klausmann
2018-02-17 22:12 Sergei Trofimovich
2018-02-14 13:29 Jason Zaman
2018-02-13 7:54 Sergei Trofimovich
2018-02-12 21:36 Thomas Deutschmann
2018-02-07 11:35 Lars Wendler
2018-02-07 9:51 Lars Wendler
2017-02-20 14:11 Michael Haubenwallner
2017-01-29 20:14 Fabian Groffen
2016-12-07 8:40 Mike Frysinger
2016-12-01 21:59 Lars Wendler
2016-02-29 8:46 Stephen Klimaszewski
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=1641460034.ef511d7814808591e6a273ea1598dcc1b3a798cc.soap@gentoo \
--to=soap@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