From: "Alon Bar-Lev" <alonbl@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/libp11/
Date: Mon, 31 Oct 2016 19:50:21 +0000 (UTC) [thread overview]
Message-ID: <1477943410.118b7db9514830c4e8bb0aef3e78f53256a16908.alonbl@gentoo> (raw)
commit: 118b7db9514830c4e8bb0aef3e78f53256a16908
Author: Alon Bar-Lev <alonbl <AT> gentoo <DOT> org>
AuthorDate: Mon Oct 31 19:49:03 2016 +0000
Commit: Alon Bar-Lev <alonbl <AT> gentoo <DOT> org>
CommitDate: Mon Oct 31 19:50:10 2016 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=118b7db9
dev-libs/libp11: fix bindist USE
Bug: 598631
Package-Manager: portage-2.3.0
dev-libs/libp11/libp11-0.4.2.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-libs/libp11/libp11-0.4.2.ebuild b/dev-libs/libp11/libp11-0.4.2.ebuild
index 2451b3e..9b9aba1 100644
--- a/dev-libs/libp11/libp11-0.4.2.ebuild
+++ b/dev-libs/libp11/libp11-0.4.2.ebuild
@@ -16,7 +16,7 @@ KEYWORDS="~alpha ~amd64 ~arm ~hppa ~ia64 ~ppc ~ppc64 ~s390 ~sh ~sparc ~x86"
IUSE="libressl bindist doc static-libs"
RDEPEND="
- !libressl? ( dev-libs/openssl:0=[bindist] )
+ !libressl? ( dev-libs/openssl:0=[bindist=] )
libressl? ( dev-libs/libressl:0= )"
DEPEND="${RDEPEND}
virtual/pkgconfig
next reply other threads:[~2016-10-31 19:50 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 19:50 Alon Bar-Lev [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-15 9:42 [gentoo-commits] repo/gentoo:master commit in: dev-libs/libp11/ Andrew Ammerlaan
2024-04-15 9:42 Andrew Ammerlaan
2024-04-15 9:00 Arthur Zamarin
2024-04-15 9:00 Arthur Zamarin
2024-04-15 9:00 Arthur Zamarin
2024-04-15 8:45 Arthur Zamarin
2024-04-15 8:43 Arthur Zamarin
2024-03-17 6:27 Ionen Wolkens
2024-02-02 6:38 Andrew Ammerlaan
2024-01-02 18:53 Andrew Ammerlaan
2023-12-07 17:03 Arthur Zamarin
2023-12-07 17:03 Arthur Zamarin
2023-11-23 17:12 Sam James
2023-11-23 17:12 Sam James
2023-10-27 13:06 Andrew Ammerlaan
2023-09-10 5:54 WANG Xuerui
2023-08-05 14:01 Arthur Zamarin
2023-08-05 11:36 Arthur Zamarin
2023-08-05 11:36 Arthur Zamarin
2023-08-05 11:36 Arthur Zamarin
2023-08-05 11:35 Arthur Zamarin
2023-07-17 22:14 Sam James
2023-07-10 16:07 Jakov Smolić
2023-07-07 3:29 Sam James
2023-07-07 0:45 Sam James
2023-02-15 5:02 Sam James
2022-12-18 19:33 Arthur Zamarin
2022-12-18 12:11 Sam James
2022-12-18 11:34 Sam James
2022-12-18 11:30 Sam James
2022-12-02 10:20 WANG Xuerui
2022-10-16 14:52 John Helmert III
2022-10-16 14:52 John Helmert III
2021-12-16 0:09 Sam James
2021-12-16 0:08 Sam James
2021-12-16 0:08 Sam James
2021-12-16 0:08 Sam James
2021-12-16 0:08 Sam James
2021-12-16 0:07 Sam James
2021-12-16 0:07 Sam James
2021-12-16 0:06 Sam James
2021-12-03 4:50 Sam James
2021-12-03 4:50 Sam James
2021-07-20 23:18 Marek Szuba
2021-05-01 7:29 Mikle Kolyada
2020-10-12 10:54 Lars Wendler
2020-01-09 9:25 Lars Wendler
2019-07-26 22:21 Aaron Bauman
2019-07-01 14:13 Alon Bar-Lev
2019-05-26 7:04 Sergei Trofimovich
2019-05-03 13:44 Mikle Kolyada
2019-05-03 13:44 Mikle Kolyada
2019-04-29 20:11 Sergei Trofimovich
2019-04-29 20:09 Sergei Trofimovich
2019-04-29 20:07 Sergei Trofimovich
2019-04-29 19:49 Sergei Trofimovich
2019-04-28 20:43 Mikle Kolyada
2019-04-28 20:34 Thomas Deutschmann
2019-04-25 5:12 Alon Bar-Lev
2019-03-26 20:05 Markus Meier
2019-03-25 22:18 Sergei Trofimovich
2019-03-24 20:25 Sergei Trofimovich
2019-03-24 20:12 Sergei Trofimovich
2019-03-24 19:44 Sergei Trofimovich
2019-03-24 10:01 Agostino Sarubbo
2019-03-23 9:58 Sergei Trofimovich
2019-03-05 7:43 Alon Bar-Lev
2018-09-27 23:55 Alon Bar-Lev
2018-06-20 18:19 Alon Bar-Lev
2017-03-25 18:11 Alon Bar-Lev
2017-03-18 13:16 Jeroen Roovers
2017-03-07 19:35 Michael Weber
2017-03-04 14:02 Agostino Sarubbo
2017-03-04 13:46 Agostino Sarubbo
2017-03-04 13:38 Agostino Sarubbo
2017-03-03 19:14 Tobias Klausmann
2016-10-28 23:39 Alon Bar-Lev
2016-06-26 0:09 Anthony G. Basile
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=1477943410.118b7db9514830c4e8bb0aef3e78f53256a16908.alonbl@gentoo \
--to=alonbl@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