From owner-freebsd-ports@freebsd.org Wed Feb 10 21:52:49 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 519C6AA5535 for ; Wed, 10 Feb 2016 21:52:49 +0000 (UTC) (envelope-from freebsdml@marino.st) Received: from shepard.synsport.net (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 3052D1542 for ; Wed, 10 Feb 2016 21:52:48 +0000 (UTC) (envelope-from freebsdml@marino.st) Received: from [192.168.1.21] (248.Red-83-39-200.dynamicIP.rima-tde.net [83.39.200.248]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by shepard.synsport.net (Postfix) with ESMTP id 7055143BB6; Wed, 10 Feb 2016 15:46:39 -0600 (CST) Subject: Re: Removing documentation To: Kevin Oberman References: <56B754A8.3030605@marino.st> <20160208064305.GB63030@server.rulingia.com> <56B8454F.8060605@marino.st> <1454923852.4807.19.camel@mathiaspicker.net> <56B8662A.2050502@marino.st> Cc: Mathias Picker , Peter Jeremy , FreeBSD Mailing List From: John Marino X-Enigmail-Draft-Status: N1110 Message-ID: <56BBAFB7.9080509@marino.st> Date: Wed, 10 Feb 2016 22:46:31 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Feb 2016 21:52:49 -0000 On 2/10/2016 10:15 PM, Kevin Oberman wrote: > > The stale configuration file issue has me a bit confused. The man page > does not make it clear just what makes a config "stale". All of my ports > are up to date as of 11:00 UTC this morning. As far as I know, all of > the configs are "current", although the actual config run may have been > for a much older version. "synth status shows 46 cases. I looked at one > (sysutils/tmux) and the options listed by "make showconfig" are no > different from those in the current Makefile, so I don't understand why > they are stale. Stale isn't the right word. You could use "invalid" or "obsolete" instead. The saved configuration does not match the current port. Imagine a month ago you run "make config". It saves the status of the 4 options on this imaginary port. Now imagine any of the following happening to the port. A) An option is added B) An option is removed C) An option default changed. D) Any other option configuration changed. Now the month-old saved configuration doesn't match the port. See the problem? Synth is the *only* tool that detects this. The rest keep using the old configuration the best they can, resulting in hard to track down bugs. Removing the saved configuration solves the problem; then Synth uses the defaults. Running "make config" also solves the problem, the configuration will match the port again. > I also have found at least one thing portmster can do that synth can't, > but I expect pkg can, so I won't complain about it until I have tried > using pkg to list all top-level ports (nothing depends on them) to use > to re-install all ports. I could list all ports, it's just that this is > a much longer list and portmaster did the job nicely with a simple > example in the man page. You don't need to list all the ports. Like you said, "pkg prime-list > my.list" and there's your top level. Or "synth upgrade" system and upgrade everything. Either approach works. The tight integration with pkg is helpful. > And, please, everyone, let's stop with the silly statements like "the > Handbook should be limited to the base system" or "a maintainer needs to > be able to fix all PRs". "All" is literal. Nobody expects all PRs to be valid. It's a moot point anyway, Torsten is now officially the maintainer (based on faith I guess) so for now there's no issue. Let's hope he is successful. John