Date: Thu, 07 Mar 2024 07:02:47 +0100 From: Baptiste Daroussin <bapt@FreeBSD.org> To: Roger Marquis <marquis@roble.com> Cc: FreeBSD-pkgbase@freebsd.org Subject: Re: pkgbase and config file merges Message-ID: <5785EAFC-0509-42A7-9FCA-F96136CE7641@FreeBSD.org> In-Reply-To: <sr13695n-05rq-1303-2792-o6p2nqsnr673@mx.roble.com> References: <DEE2B944-F1DB-4BA5-AF6B-144507993A4D@yahoo.com> <C0BD4501-902C-4F7A-92F0-96931D419AC8@FreeBSD.org> <sr13695n-05rq-1303-2792-o6p2nqsnr673@mx.roble.com>
index | next in thread | previous in thread | raw e-mail
Le 6 mars 2024 23:09:07 GMT+01:00, Roger Marquis <marquis@roble.com> a écrit : >On Wed, 6 Mar 2024, Baptiste Daroussin wrote: >> .pkgsave once you have boostrapped you should not have any. > >Bootstrapped what though? Whether pkgbase had been previously installed >is not the issue as we expect some pkgbase installs will be to existing >systems, with existing configurations. These configurations should not >be overwritten (but may be patched). > >Not being able to think of a scenario where overwriting existing configs >would be the expected much less desired behavior, I'm wondering what >scenarios would require this bootstrap behavior? > >Roger Pkgbase behave exactly the same as etcupdate and or freebsd-update, this is what I am saying Bapthome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5785EAFC-0509-42A7-9FCA-F96136CE7641>