From: "Michael Palimaka" <kensington@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-i18n/enca/
Date: Sun, 29 Jan 2017 17:01:36 +0000 (UTC) [thread overview]
Message-ID: <1485709287.381d1c968ab2b336f231da6d8ce9e12a8b3bb42a.kensington@gentoo> (raw)
commit: 381d1c968ab2b336f231da6d8ce9e12a8b3bb42a
Author: Ilya Tumaykin <itumaykin <AT> gmail <DOT> com>
AuthorDate: Sat Jan 21 15:19:43 2017 +0000
Commit: Michael Palimaka <kensington <AT> gentoo <DOT> org>
CommitDate: Sun Jan 29 17:01:27 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=381d1c96
app-i18n/enca: use common notation in string comparisons in 1.19-r1
Prevents me from trying to remember why it wasn't done the usual way.
The reason is still unknown, because this is a ditto change:
https://www.gnu.org/software/bash/manual/html_node/Conditional-Constructs.html
Package-Manager: Portage-2.3.3, Repoman-2.3.1
app-i18n/enca/enca-1.19-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app-i18n/enca/enca-1.19-r1.ebuild b/app-i18n/enca/enca-1.19-r1.ebuild
index b9cf4b7..8fbddd1 100644
--- a/app-i18n/enca/enca-1.19-r1.ebuild
+++ b/app-i18n/enca/enca-1.19-r1.ebuild
@@ -41,7 +41,7 @@ src_prepare() {
multilib_src_configure() {
# Workaround GCC-4.8 brokenness. See Gentoo bug 501386.
- if tc-is-gcc && [[ $(gcc-version) = '4.8' ]]; then
+ if tc-is-gcc && [[ $(gcc-version) == "4.8" ]]; then
replace-flags -O[3-9] -O2
fi
next reply other threads:[~2017-01-29 17:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-29 17:01 Michael Palimaka [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-14 10:48 [gentoo-commits] repo/gentoo:master commit in: app-i18n/enca/ Yixun Lan
2021-01-24 13:50 Sam James
2021-01-24 13:35 Sam James
2021-01-24 13:33 Sam James
2021-01-23 22:55 Sam James
2021-01-22 16:53 Agostino Sarubbo
2021-01-22 2:12 Sam James
2021-01-22 1:50 Sam James
2021-01-06 13:13 Fabian Groffen
2021-01-04 5:34 Sam James
2021-01-04 5:27 Sam James
2020-05-16 14:42 Mike Gilbert
2017-07-23 1:11 Michael Palimaka
2017-02-03 20:01 Jeroen Roovers
2016-11-16 9:10 Tobias Klausmann
2016-11-13 8:54 Markus Meier
2016-09-20 20:55 Yixun Lan
2016-09-19 23:34 Yixun Lan
2016-09-19 23:34 Yixun Lan
2016-09-19 23:34 Yixun Lan
2016-08-21 17:28 Patrice Clement
2016-01-07 17:05 Lars Wendler
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=1485709287.381d1c968ab2b336f231da6d8ce9e12a8b3bb42a.kensington@gentoo \
--to=kensington@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