From owner-svn-src-head@freebsd.org Sat May 13 16:51:46 2017 Return-Path: Delivered-To: svn-src-head@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 5EC90D6B7CC; Sat, 13 May 2017 16:51:46 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3EEFB128E; Sat, 13 May 2017 16:51:46 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1033) id 5AB861F6E; Sat, 13 May 2017 16:51:45 +0000 (UTC) Date: Sat, 13 May 2017 16:51:45 +0000 From: Alexey Dokuchaev To: Ian Lepore Cc: rgrimes@freebsd.org, Ngie Cooper , svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r318250 - in head: etc etc/newsyslog.conf.d etc/syslog.d tools/build/mk Message-ID: <20170513165145.GC84947@FreeBSD.org> References: <201705131537.v4DFbgWV045290@pdx.rh.CN85.dnsmgr.net> <1494692660.59865.85.camel@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1494692660.59865.85.camel@freebsd.org> User-Agent: Mutt/1.7.1 (2016-10-04) X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 May 2017 16:51:46 -0000 On Sat, May 13, 2017 at 10:24:20AM -0600, Ian Lepore wrote: > ... > The evolution for years has been away from monolithic config files > containing a mashup of values for unrelated subsystems and towards > .conf.d directories containing many single-subject files. This "evolution" had probably originated in people's minds who know little about software development and maintenance. And FWIW, newsyslog files are not about "unrelated subsystems", it's about one subsystem responsible for log rotation. Speaking of "unrelated subsystems", /etc/rc.conf is a living manifestation of how "unrelated subsystems" can be configured in a single file and, mind you, everyone is being quite happy about it. > The monolithic files are difficult to edit Quite on the contrary: monolithic files are much easier to edit and keep track of by a human being (system operator). > and otherwise manage programmatically, and especially difficult to manage > in terms of software packaging and software updates. Please don't mix "difficult to edit" and "manage programmatically". As I have said, having support for "include *.conf.d" makes sense for 3rd-party software (read: ports), but has little need for the base, and IMHO brings more maintenance burden than any benefit. ./danfe