From owner-freebsd-ports@freebsd.org  Wed Apr  6 14:47:27 2016
Return-Path: <owner-freebsd-ports@freebsd.org>
Delivered-To: freebsd-ports@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id B6831B06949
 for <freebsd-ports@mailman.ysv.freebsd.org>;
 Wed,  6 Apr 2016 14:47:27 +0000 (UTC) (envelope-from lists@opsec.eu)
Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3])
 by mx1.freebsd.org (Postfix) with ESMTP id A5CF91E3F
 for <freebsd-ports@freebsd.org>; Wed,  6 Apr 2016 14:47:27 +0000 (UTC)
 (envelope-from lists@opsec.eu)
Received: by mailman.ysv.freebsd.org (Postfix)
 id A1778B06948; Wed,  6 Apr 2016 14:47:27 +0000 (UTC)
Delivered-To: ports@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id A1207B06947
 for <ports@mailman.ysv.freebsd.org>; Wed,  6 Apr 2016 14:47:27 +0000 (UTC)
 (envelope-from lists@opsec.eu)
Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 645A21E3E
 for <ports@freebsd.org>; Wed,  6 Apr 2016 14:47:27 +0000 (UTC)
 (envelope-from lists@opsec.eu)
Received: from pi by home.opsec.eu with local (Exim 4.86_2 (FreeBSD))
 (envelope-from <lists@opsec.eu>)
 id 1anojv-0008UQ-Aj; Wed, 06 Apr 2016 16:47:27 +0200
Date: Wed, 6 Apr 2016 16:47:27 +0200
From: Kurt Jaeger <lists@opsec.eu>
To: Jim Ohlstein <jim@ohlste.in>
Cc: ports@freebsd.org
Subject: Re: Committer needed for PR 208029
Message-ID: <20160406144727.GP35640@home.opsec.eu>
References: <498CA3F8-15EF-45BD-880C-241F83CBE3DD@waschbuesch.de>
 <20160405185159.GK35640@home.opsec.eu>
 <20160405200835.GM35640@home.opsec.eu> <57042958.5010701@sorbs.net>
 <C96569DA-ADC5-4BE0-819A-7375C3F50D8E@waschbuesch.de>
 <20160406044431.GO35640@home.opsec.eu> <570517F1.5020305@ohlste.in>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <570517F1.5020305@ohlste.in>
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Apr 2016 14:47:27 -0000

Hi!

> This is much ado about nothing. The "WITH_OPENSSL_PORT" option is there 
> for just this purpose and is used in many ports.

In 9.x this is sometimes a problem, if port X builds in variant 1
and port Y depends/links on X, but builds in variant 2. So it's
a temporary solution for 9.x and will be solved when 9.x is EOL'ed.

I'm not sure how this is solved in 10.x/11.x, probably the base SSL
is much more up2date.

> Forcing users who want to use this port to use OpenSSL from ports for 
> ALL ports is overkill.

> Think about official packages. Are ALL packages built against OpenSSL 
> from ports, or only those that need them? It's the latter, of course. 
> Are they incompatible in production? No.

There are grey areas, and I guess it will be like that for 9.x.

-- 
pi@opsec.eu            +49 171 3101372                         4 years to go !