Date: Mon, 13 Nov 2017 12:51:44 -0700 From: Brad Davis <brd@FreeBSD.org> To: John Baldwin <jhb@freebsd.org> Cc: Glen Barber <gjb@freebsd.org>, freebsd-pkgbase@freebsd.org, Will Andrews <will@FreeBSD.org> Subject: Re: Problems with packaging /etc and etcupdate(8) Message-ID: <20171113195144.GH53537@corpmail.liquidneon.com> In-Reply-To: <1972909.hTPcQf8OeH@ralph.baldwin.cx> References: <20170927163012.GA99112@FreeBSD.org> <20171113172054.GA23670@FreeBSD.org> <1972909.hTPcQf8OeH@ralph.baldwin.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Nov 13, 2017 at 09:26:49AM -0800, John Baldwin wrote: > I had assumed that in a pkgbase setup, one wouldn't use etcupdate or mergemaster. > Instead, my understanding is that pkg was going to "learn" about configuration > files and would grow etcupdate-like functionality to merge in changes to configuration > files during upgrades (and would also support 'pkg confdiff', etc. so that > 'pkg confdiff -a' would replace 'etcupdate diff' for example, but would also support > packages built from ports, not just base system conf files). Each pkgbase package > would contain its associated /etc files as configuration files in this scheme. To that end Will and I have been working on a patch to move all files in head/etc/ to the places they belong. I am probably ~75% of the way through them so far. Once I get the last bit wrapped up, I will post a review. Regards, Brad Davis
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20171113195144.GH53537>