Date: Sat, 22 Nov 2025 10:57:59 +0000 From: void <void@f-m.fm> To: freebsd-current@freebsd.org Subject: Re: changing from pkgbase to regularbase Message-ID: <aSGXN6-JcvYTg2jv@int21h> In-Reply-To: <aSETbVSLxcDa5ssB@amaryllis.le-fay.org> References: <aR3Rc_5llfvlEjIo@int21h> <aSEGPTtrfV29u9R9@amaryllis.le-fay.org> <71e4b46c-8d69-451d-92ca-79316ffc4b63@app.fastmail.com> <aSETbVSLxcDa5ssB@amaryllis.le-fay.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Nov 22, 2025 at 01:35:41AM +0000, Lexi Winter wrote: >probably by making the warning more difficult to override... A retrograde step IMO. The warning was sufficient to prevent installkernel-by-accident. Which I think was the goal. Accidental foot-shooting. There is no need IMO for further guardrails when the goal in this case was to move back to a traditional system. >there is no supported method to "depkgbasify" a system. IMO there should be. >the correct method to not use pkgbase is to not select pkgbase when >installing the system. People change their minds. From an immediate "oops" to a repurposing of the installation further along the road. Just about everything within FreeBSD can be changed post-installation. Why this issue with pkgbase? >an unofficial and unsupported, but functional, workaround is to install >the system with pkgbase, then immediately run "rm -rf /var/db/pkg" >before installing any ports, which will leave you with a system mostly >identical to a distribution set install. you will need to manually >bootstrap etcupdate after doing this, since pkgbase doesn't install the >etcupdate data. That's good to know. It'd be useful to have this in the handbook somewhere. --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aSGXN6-JcvYTg2jv>