Date: Sun, 18 Dec 2016 14:18:18 +0000 From: Grzegorz Junka <list1@gjunka.com> To: freebsd-ports@freebsd.org Subject: Re: The ports collection has some serious issues Message-ID: <445d2a42-b6e0-4495-ce34-baed27db5461@gjunka.com> In-Reply-To: <b3c3d33c-439f-59cf-fa60-b025428996d4@marino.st> References: <b21222a1-4940-1a44-0693-8c7803798a58@marino.st> <58558519.3080509@abinet.ru> <b3c3d33c-439f-59cf-fa60-b025428996d4@marino.st>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?445d2a42-b6e0-4495-ce34-baed27db5461>