On Mon, Oct 20, 2025 at 08:59:36AM -0600, Warner Losh wrote: > On Mon, Oct 20, 2025, 8:42 AM Lexi Winter <[email protected]> wrote: > > > John Baldwin wrote in <[email protected]>: > > > On 10/17/25 15:14, Lexi Winter wrote: > > > > Makefile: Don't allow install{world,kernel} with pkgbase > > > > > > Can we document how users who want to build from source can do so from a > > new installation > > > that uses pkgbase? I guess it is something like: > > > > > > - pkg install sources if not already (or git clone the right branch/tag) > > > - etcupdate bootstrap > > > - <destroy the pkgbase repo> (clearly can't just use pkg delete with a > > glob, so need > > > something else) > > > > this should eventually be in the Handbook. > > > Install* should eventually just do the right thing like ports: stage the > packages, make the packages and the install from the packages. 16 time > frame, though.
Agreed with Warner here. If pkgbase is being used, it seems logical
that installworld/installkernel would create a new (or update) pkgbase
repo.
Otherwise, I can imagine a sceneario for HardenedBSD users
specifically who have used pkgbase in the past, but now wish to do a
src-based update. I feel like I myself am going to be answering an
unending stream of "why doesn't install{kernel,world} work on
HardenedBSD like it has always in the past?"
I'm somewhat thinking of reverting this commit until
install{kernel,world} are taught the notion of pkgbase. It just seems
like the kind of thing that's gonna surprise our users (in a
not-so-fun way.)
Thanks,
--
Shawn Webb
Cofounder / Security Engineer
HardenedBSD
Signal Username: shawn_webb.74
Tor-ified Signal: +1 303-901-1600 / shawn_webb_opsec.50
https://git.hardenedbsd.org/hardenedbsd/pubkeys/-/raw/master/Shawn_Webb/03A4CBEBB82EA5A67D9F3853FF2E67A277F8E1FA.pub.asc
signature.asc
Description: PGP signature
