Date: Fri, 11 Aug 2017 12:28:23 +0300 From: Garrett Wollman <wollman@csail.mit.edu> To: freebsd-pkgbase@freebsd.org Subject: Re: pkgbase update and progress Message-ID: <F8F6083C-C299-40C0-9631-89680FCD3D1D@csail.mit.edu> In-Reply-To: <8eb2fbb1-b9e2-e343-b2ba-fcdaa425c18b@FreeBSD.org> (sfid-20170811_03575_2566223D) References: <20170810140615.GD63224@FreeBSD.org> <1218488026.1377609.1502378299872.JavaMail.zimbra@ixsystems.com> <20170810152151.GB82820@FreeBSD.org> <f2b904f8-af18-9d5b-9d8d-b99214d33f20@FreeBSD.org> <CAOc73CDyKcXzSO-EfZLp9oHkXxq8jxZKGK5Ox69TynadhErzsg@mail.gmail.com> <8eb2fbb1-b9e2-e343-b2ba-fcdaa425c18b@FreeBSD.org> (sfid-20170811_03575_2566223D)
next in thread | previous in thread | raw e-mail | index | archive | help
On August 11, 2017 10:57:35 AM GMT+03:00, Matthew Seaman <matthew@FreeBSD= =2Eorg> wrote: >I think etcupdate(8) has a longer history and people are more familiar >with it whereas the 3-way merge code in pkg(8) has been exercised >relatively rarely=2E There's also considerations about how this would >fit >into various different workflows -- everything from people that only >ever download the standard pre-compiled packages for a release, to >developers trying to cross-build highly customized embedded systems=2E >Having a 'merge' step that is separated from the 'install' step seems >advantageous in that it allows a point where people can substitute in >their own alternatives for managing /etc files=2E Maybe it should be called a "configure" phase for consistency with other p= ackage managers=2E
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F8F6083C-C299-40C0-9631-89680FCD3D1D>