From owner-freebsd-ports@FreeBSD.ORG Wed Apr 1 21:37:41 2015 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 40A6F61A; Wed, 1 Apr 2015 21:37:41 +0000 (UTC) Received: from mail.madpilot.net (grunt.madpilot.net [78.47.145.38]) (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 E8F4ADBA; Wed, 1 Apr 2015 21:37:40 +0000 (UTC) Received: from mail (mail [192.168.254.3]) by mail.madpilot.net (Postfix) with ESMTP id 3lHLKV4fgnzZrM; Wed, 1 Apr 2015 23:30:22 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=madpilot.net; h= content-transfer-encoding:content-type:content-type:in-reply-to :references:subject:subject:mime-version:user-agent:from:from :date:date:message-id:received:received; s=mail; t=1427923820; x=1429738221; bh=PY+rixI4it9sFUhTnFq6Pkso3P8HUXgofHVr6XURPiQ=; b= kkc2Rx6pnujSD8kiIzrLX5Hp6n5Iu7rwb9CW/kgJulnA6iqOisakFawb+9N77twg 2zBYKierH8wEd4w8S5h0els9OkcsPJ3wfrnSGyuq89Z4gsZQQk0XisXwO/eVQlFJ KzGCV0qnxxO12MxTJZ2Kq8NlLQQ+kYV8b40sfPehZE4= Received: from mail.madpilot.net ([192.168.254.3]) by mail (mail.madpilot.net [192.168.254.3]) (amavisd-new, port 10024) with ESMTP id u_dasoKon-wR; Wed, 1 Apr 2015 23:30:20 +0200 (CEST) Received: from tommy.madpilot.net (micro.madpilot.net [88.149.173.206]) by mail.madpilot.net (Postfix) with ESMTPSA; Wed, 1 Apr 2015 23:30:20 +0200 (CEST) Message-ID: <551C636C.1090000@madpilot.net> Date: Wed, 01 Apr 2015 23:30:20 +0200 From: Guido Falsi User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: Yuri , Jung-uk Kim , "ports@freebsd.org" Subject: Re: Pourdriere produces faulty build results due to bsd.openssl.mk bug References: <551C5C4C.5090707@rawbw.com> <551C6051.4060803@FreeBSD.org> <551C616C.8080503@rawbw.com> In-Reply-To: <551C616C.8080503@rawbw.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: Dirk Meyer , Bryan Drewery X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2015 21:37:41 -0000 On 04/01/15 23:21, Yuri wrote: > On 04/01/2015 14:17, Jung-uk Kim wrote: >> I know bsd.openssl.mk has been broken for very long time. For example, >> >> http://docs.freebsd.org/cgi/mid.cgi?50108FEF.3030405 >> >> However, I am not sure whether entirely removing it is the best way >> going forward. > > I mean, removing of the dependency on base. Ports should use only > openssl port. > > If you think this isn't a good idea, and ports should still occasionally > use base openssl, would you care to explain why you think so? I'm not in the position of taking such decisions, but based on some experience and quick tests I have discovered that changing the default would cause ports now working to break. I generally agree with your idea that ports should use ports ssl, but making this switch is more difficult than just changing a variable. Some real testing is needed, and just exp-runs would not suffice, most software would show misbehavior only at runtime. Some examples of things that could (and will) go wrong: - ports silently linking to base ssl due to weirdness in their build scripts - ports linking to other libraries in base which are linked to base ssl, causing conflicts - ports interacting with base parts, which are using base ssl. All this without accounting for eventual ports who do need older ssl to work, causing further mixing. I have experienced or seen reports about all tree examples. Also, you could have a look at this bug: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198788 -- Guido Falsi