From owner-freebsd-ports@freebsd.org Sun Dec 18 14:35:19 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 63721C87359 for ; Sun, 18 Dec 2016 14:35:19 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from msa1.earth.yoonka.com (yoonka.com [185.24.122.233]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "msa1.earth.yoonka.com", Issuer "msa1.earth.yoonka.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 10B2B96 for ; Sun, 18 Dec 2016 14:35:18 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from crayon2.yoonka.com (crayon2.yoonka.com [10.70.7.20]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id uBIEIIKJ056890 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Sun, 18 Dec 2016 14:18:18 GMT (envelope-from list1@gjunka.com) Subject: Re: The ports collection has some serious issues To: freebsd-ports@freebsd.org References: <58558519.3080509@abinet.ru> From: Grzegorz Junka Message-ID: <445d2a42-b6e0-4495-ce34-baed27db5461@gjunka.com> Date: Sun, 18 Dec 2016 14:18:18 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed 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, 18 Dec 2016 14:35:19 -0000 On 17/12/2016 18:51, John Marino wrote: > On 12/17/2016 12:34, abi wrote: >> >>>> 2. It doesn't provide dialog for port options, so >>>> 2.1 I don't receive information if port options have changed. I don't >>>> know what else will be pulled to my system after port tree update. >>> >>> which of course is a false statement. >>> If you set port options which then change, Synth will stop and tell >>> you to reconfigure or remove the saved port options. >> >> Not at all. For example, let's assume I go recommended way and have >> options for ports with not default settings. Let's say, I have perl with >> default options (no OPTIONS file). Let's say port maintainer adds new >> option, [NSA Backdoor] >> Perl will be silently compiled with that option, right? > > Yes. If you don't explicitly save the options then Synth has no way > to detect a change in options. Isn't poudriere automatically saving the options file when building a new port with default options (i.e. when no options have been specified)? And also, aren't the selected options available in the resulted pkg file, so that synth could look them up there? Grzegorz