From: "Anthony G. Basile" <blueness@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-crypt/johntheripper/
Date: Fri, 3 Jun 2016 11:03:43 +0000 (UTC) [thread overview]
Message-ID: <1464951936.f96e8a6179b60e178a285748cf8b116c0285d26e.blueness@gentoo> (raw)
commit: f96e8a6179b60e178a285748cf8b116c0285d26e
Author: Anthony G. Basile <blueness <AT> gentoo <DOT> org>
AuthorDate: Fri Jun 3 11:05:21 2016 +0000
Commit: Anthony G. Basile <blueness <AT> gentoo <DOT> org>
CommitDate: Fri Jun 3 11:05:36 2016 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f96e8a61
app-crypt/johntheripper: add libressl support
Package-Manager: portage-2.2.28
app-crypt/johntheripper/johntheripper-1.7.9-r10.ebuild | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/app-crypt/johntheripper/johntheripper-1.7.9-r10.ebuild b/app-crypt/johntheripper/johntheripper-1.7.9-r10.ebuild
index b455023..071fe1a 100644
--- a/app-crypt/johntheripper/johntheripper-1.7.9-r10.ebuild
+++ b/app-crypt/johntheripper/johntheripper-1.7.9-r10.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2015 Gentoo Foundation
+# Copyright 1999-2016 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Id$
@@ -21,7 +21,7 @@ LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~alpha ~amd64 ~arm ~hppa ~mips ~ppc ~ppc64 ~sparc ~x86 ~x86-fbsd ~x86-interix ~amd64-linux ~x86-linux ~ppc-macos"
#Remove AltiVec USE flag. Appears to be an upstream issue.
-IUSE="cuda custom-cflags -minimal cpu_flags_x86_mmx mozilla mpi opencl openmp cpu_flags_x86_sse2"
+IUSE="cuda custom-cflags -minimal cpu_flags_x86_mmx libressl mozilla mpi opencl openmp cpu_flags_x86_sse2"
REQUIRED_USE="openmp? ( !minimal )
mpi? ( !minimal )
cuda? ( !minimal )
@@ -29,7 +29,10 @@ REQUIRED_USE="openmp? ( !minimal )
mozilla? ( !minimal )"
DEPEND="sys-libs/zlib
- !minimal? ( >=dev-libs/openssl-0.9.7:0 )
+ !minimal? (
+ !libressl? ( dev-libs/openssl:0= )
+ libressl? ( dev-libs/libressl:0= )
+ )
mpi? ( virtual/mpi )
cuda? ( x11-drivers/nvidia-drivers
dev-util/nvidia-cuda-toolkit:= )
next reply other threads:[~2016-06-03 11:03 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 11:03 Anthony G. Basile [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-11-02 20:24 [gentoo-commits] repo/gentoo:master commit in: app-crypt/johntheripper/ Craig Andrews
2018-11-02 20:24 Craig Andrews
2018-11-27 17:52 Rick Farina
2018-12-13 15:34 Rick Farina
2018-12-18 21:40 Rick Farina
2018-12-18 21:40 Rick Farina
2019-05-07 6:26 Sergei Trofimovich
2019-05-08 6:25 Sergei Trofimovich
2019-05-08 14:38 Tobias Klausmann
2019-05-12 21:57 Sergei Trofimovich
2019-05-12 22:03 Sergei Trofimovich
2019-05-13 17:02 Mikle Kolyada
2019-05-15 15:17 Mikle Kolyada
2019-05-15 15:17 Mikle Kolyada
2019-06-05 21:19 Andreas Sturmlechner
2021-01-07 8:20 Fabian Groffen
2021-04-03 23:07 Sam James
2021-11-19 11:33 Sam James
2022-01-05 10:01 David Seifert
2022-05-14 21:30 David Seifert
2023-08-19 22:40 Rick Farina
2023-08-19 22:40 Rick Farina
2023-08-21 20:56 Rick Farina
2023-08-21 20:56 Rick Farina
2023-08-21 20:56 Rick Farina
2024-12-01 19:03 Arthur Zamarin
2024-12-01 19:06 Arthur Zamarin
2024-12-01 22:36 Jakov Smolić
2024-12-24 5:00 Sam James
2025-02-15 9:29 Ulrich Müller
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=1464951936.f96e8a6179b60e178a285748cf8b116c0285d26e.blueness@gentoo \
--to=blueness@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