From owner-freebsd-ports@freebsd.org Thu Oct 27 18:36:30 2016 Return-Path: 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 4828FC24A4E for ; Thu, 27 Oct 2016 18:36:30 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from mail.infocus-llc.com (mail.infocus-llc.com [199.15.120.13]) (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 18F8AB0E; Thu, 27 Oct 2016 18:36:29 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (c-75-65-60-66.hsd1.ms.comcast.net [75.65.60.66]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.tarragon.infocus-llc.com (Postfix) with ESMTPSA id 3t4bFS4cJbz1Tp; Thu, 27 Oct 2016 13:36:28 -0500 (CDT) Received: by draco.over-yonder.net (Postfix, from userid 100) id 3t4bFS0B0hz4cc; Thu, 27 Oct 2016 13:36:28 -0500 (CDT) Date: Thu, 27 Oct 2016 13:36:27 -0500 From: "Matthew D. Fuller" To: Mathieu Arnold Cc: David Demelier , Don Lewis , mad@madpilot.net, freebsd-ports@freebsd.org Subject: Re: lighttpd does not pull OpenSSL dependency Message-ID: <20161027183627.GA35998@over-yonder.net> References: <201610252214.u9PME6br070248@gw.catspoiler.org> <7fb24c94-1efa-d1b5-9028-8dec8330e543@FreeBSD.org> <20161027150035.GP79735@over-yonder.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.6.1-fullermd.4 (2016-04-27) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Oct 2016 18:36:30 -0000 On Thu, Oct 27, 2016 at 06:35:25PM +0200 I heard the voice of Mathieu Arnold, and lo! it spake thus: > > Well, that is another problem, and you are right, OpenSSL's shlib > should have been bumped, blame the former maintainer for that. I'll > talk to the new maintainer about that. The argument could be made that (a) OpenSSL 1.1.0 is gonna be released and brought into ports Any Day Now and it already has a different shlibver (and that would get us back on parity with upstream, for what that's worth), and (b) by the time 11-CURRENT (where you gotta expect bumps) becomes 11-STABLE, base openssl will be private-ized anyway. It's a good couple theories... -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.