From owner-freebsd-ports@freebsd.org Sun Dec 18 15:00:43 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 9BBE5C87BF4 for ; Sun, 18 Dec 2016 15:00:43 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 8932E1054 for ; Sun, 18 Dec 2016 15:00:43 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: by mailman.ysv.freebsd.org (Postfix) id 85B02C87BF3; Sun, 18 Dec 2016 15:00:43 +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 8555BC87BF2 for ; Sun, 18 Dec 2016 15:00:43 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from shepard.synsport.com (mail.synsport.com [208.69.230.148]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 649781053 for ; Sun, 18 Dec 2016 15:00:42 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from [127.0.0.1] (ip72-204-83-236.fv.ks.cox.net [72.204.83.236]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by shepard.synsport.com (Postfix) with ESMTP id 6869643BA5; Sun, 18 Dec 2016 08:59:32 -0600 (CST) From: John Marino Reply-To: marino@freebsd.org To: "ports@FreeBSD.org" , listl@gjunka.com Subject: The ports collection has some serious issues Message-ID: <9b9b1fb6-29c5-50fa-38f8-d3e7fc287697@marino.st> Date: Sun, 18 Dec 2016 09:00:41 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 161217-0, 12/17/2016), Outbound message X-Antivirus-Status: Clean 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 15:00:43 -0000 Grzegorz Junka wrote: > 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 [please keep me CC'd, I can't respond easily if not] Synth does look up package options. It compares it with the currently options specifications and will obsolete the package if they don't match exactly. Synth intentionally does not store option files. It will use option files that are pre-created for it (the lack of stored options means "use the defaults"). The behavior is intentional and it results in synth rarely having to break a scan and stop and most people want this, but it just so happens that abi wanted the exact opposite behavior. It's actually the first time I've heard somebody wanting the "explicitly save options" behavior because it's quite disruptive in practice. [1] John [1] I wonder how hard it would be for Synth to optionally create an saved options file (outside of the ports framework) when the package is successfully built. It's likely possible (non-default behavior) --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus