From owner-freebsd-ports@freebsd.org Sun Oct 15 22:31:31 2017 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 17C61E4C655 for ; Sun, 15 Oct 2017 22:31:31 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 0155D63461 for ; Sun, 15 Oct 2017 22:31:31 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Received: by mailman.ysv.freebsd.org (Postfix) id F1D07E4C654; Sun, 15 Oct 2017 22:31:30 +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 F1734E4C653 for ; Sun, 15 Oct 2017 22:31:30 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Received: from echo.brtsvcs.net (echo.brtsvcs.net [IPv6:2607:f740:c::4ae]) (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 AA1DC63460; Sun, 15 Oct 2017 22:31:30 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Received: from chombo.houseloki.net (c-73-240-250-185.hsd1.or.comcast.net [73.240.250.185]) by echo.brtsvcs.net (Postfix) with ESMTPS id 0530D38F48; Sun, 15 Oct 2017 15:31:30 -0700 (PDT) Received: from [IPv6:fe80::7102:4df8:1f13:5c55] (unknown [IPv6:fe80::7102:4df8:1f13:5c55]) by chombo.houseloki.net (Postfix) with ESMTPSA id CE1471AE8; Sun, 15 Oct 2017 15:31:28 -0700 (PDT) Subject: Re: Why ports are allowed to be linked with base OpenSSL? To: Baptiste Daroussin , Yuri Cc: "ports@freebsd.org" References: <20171015184133.qw342awio6svrw7v@ivaldir.net> From: Mel Pilgrim Message-ID: <454e2110-9a36-c9f3-e102-ff538abbd616@bluerosetech.com> Date: Sun, 15 Oct 2017 15:31:29 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <20171015184133.qw342awio6svrw7v@ivaldir.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit 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: Sun, 15 Oct 2017 22:31:31 -0000 On 10/15/2017 11:41, Baptiste Daroussin wrote: > On Sun, Oct 15, 2017 at 06:15:24PM +0000, Yuri wrote: >> Uses/ssl.mk allows SSL_DEFAULT=base. I know this has been discussed here >> before, but why is this even allowed? If some ports are built with >> SSL_DEFAULT=base, and some with SSL_DEFAULT=openssl, this will obviously >> cause conflicts when two incompatible openssl libraries will be mapped into >> the same process. >> >> >> Isn't it better to only allow port OpenSSL for ports, and disallow base >> OpenSSL in ports, so that there will be homogeneity of openssl? >> > > First the default SSL is supposed to be for the entire ports tree, not only for > a bunch of ports. > > Second, yes that is the plan but it takes time and it is not that easy to make > it happen :) What are the current roadblocks to setting SSL_DEFAULT=openssl in ssl.mk? Is there a list of ports that don't compile with the ports openssl?