From: "Justin Lecher" <jlec@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-misc/axel/
Date: Thu, 15 Oct 2015 12:31:18 +0000 (UTC) [thread overview]
Message-ID: <1444911953.db41360e6524daae46c9ad0d65c65df2fc5cb065.jlec@gentoo> (raw)
commit: db41360e6524daae46c9ad0d65c65df2fc5cb065
Author: Justin Lecher <jlec <AT> gentoo <DOT> org>
AuthorDate: Thu Oct 15 12:25:53 2015 +0000
Commit: Justin Lecher <jlec <AT> gentoo <DOT> org>
CommitDate: Thu Oct 15 12:25:53 2015 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=db41360e
net-misc/axel: Fix passing of nls configure option
thanks René Rhéaume for the patch
Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=562534
Package-Manager: portage-2.2.23
Signed-off-by: Justin Lecher <jlec <AT> gentoo.org>
net-misc/axel/axel-2.4-r3.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net-misc/axel/axel-2.4-r3.ebuild b/net-misc/axel/axel-2.4-r3.ebuild
index 632ffe5..ecf041c 100644
--- a/net-misc/axel/axel-2.4-r3.ebuild
+++ b/net-misc/axel/axel-2.4-r3.ebuild
@@ -35,7 +35,7 @@ src_configure() {
local myconf=()
use debug && myconf+=( --debug=1 )
- use nls && myconf+=( --i18n=$(usex nls 1 0) )
+ myconf+=( --i18n=$(usex nls 1 0) )
econf \
--strip=0 \
${myconf[@]}
next reply other threads:[~2015-10-15 12:31 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 12:31 Justin Lecher [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-25 7:34 [gentoo-commits] repo/gentoo:master commit in: net-misc/axel/ Petr Vaněk
2024-10-24 14:42 Sam James
2024-10-24 14:42 Sam James
2024-10-24 14:07 Arthur Zamarin
2024-10-24 14:07 Arthur Zamarin
2024-10-24 14:07 Arthur Zamarin
2024-09-14 13:14 Petr Vaněk
2024-09-14 13:14 Petr Vaněk
2024-09-14 13:14 Petr Vaněk
2024-03-01 13:46 Arthur Zamarin
2023-03-29 20:51 Piotr Karbowski
2023-02-27 9:02 WANG Xuerui
2022-11-06 8:05 Agostino Sarubbo
2022-11-06 4:00 Sam James
2022-11-06 4:00 Sam James
2022-11-06 4:00 Sam James
2022-11-06 4:00 Sam James
2022-10-17 23:34 Sam James
2022-06-23 21:03 Piotr Karbowski
2022-06-23 21:03 Piotr Karbowski
2022-04-03 12:36 Piotr Karbowski
2022-04-01 13:55 Marek Szuba
2021-05-02 12:09 Mikle Kolyada
2021-02-07 1:07 Sam James
2021-02-04 14:42 Agostino Sarubbo
2021-02-04 14:09 Sam James
2021-02-04 8:00 Sam James
2021-02-04 7:59 Sam James
2020-11-25 21:52 Piotr Karbowski
2020-06-14 10:00 Piotr Karbowski
2020-06-06 21:17 Piotr Karbowski
2020-06-04 6:23 Agostino Sarubbo
2020-06-01 20:51 Sergei Trofimovich
2020-05-31 19:12 Sergei Trofimovich
2020-05-31 8:19 Sergei Trofimovich
2020-04-08 14:42 Piotr Karbowski
2020-04-08 9:54 Agostino Sarubbo
2020-04-08 9:53 Agostino Sarubbo
2020-04-08 9:51 Agostino Sarubbo
2020-04-08 9:50 Agostino Sarubbo
2020-04-07 20:20 Piotr Karbowski
2020-04-07 19:37 Piotr Karbowski
2020-02-21 22:31 Piotr Karbowski
2020-02-21 20:52 Piotr Karbowski
2019-04-27 20:28 David Seifert
2017-10-27 22:42 Patrice Clement
2017-10-27 22:42 Patrice Clement
2017-10-27 22:42 Patrice Clement
2017-10-03 21:34 Patrice Clement
2017-01-05 22:50 Justin Lecher
2015-11-05 12:57 Justin Lecher
2015-10-04 10:14 Agostino Sarubbo
2015-10-03 7:06 Jeroen Roovers
2015-10-01 12:37 Agostino Sarubbo
2015-09-29 11:36 Justin Lecher
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=1444911953.db41360e6524daae46c9ad0d65c65df2fc5cb065.jlec@gentoo \
--to=jlec@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