Re: git: 74a6bb524e5b - main - Makefile: Don't allow install{world,kernel} with pkgbase

From: Warner Losh <imp_at_bsdimp.com>
Date: Mon, 20 Oct 2025 14:59:36 UTC
On Mon, Oct 20, 2025, 8:42 AM Lexi Winter <ivy@freebsd.org> wrote:

> John Baldwin wrote in <228220a0-c819-4c51-92d3-5357e925c81d@FreeBSD.org>:
> > 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.

Warner

i'm not sure what the current
> state of that documentation is right now, but i know there are at least
> some important bits missing, probably including this.
>
> for 15.0, you should simply not use pkgbase to install the new system,
> since dists are still supported.  if you *have* to use pkgbase, e.g.
> you're using media that doesn't include dist sets and can't do an online
> installation, then you can delete /var/db/pkg immediately after booting
> into the new system, before installing any ports.  the system will then
> be more-or-less identical to one installed from dist sets, so you can
> follow the usual instructions for updating from source.
>
> for 16.0, the plan is to remove support for dist sets from the release
> media[0], so we'll probably want a way to do this automatically in the
> installer.  that's TBD, but i'm planning on doing some work on this part
> of the release media once 15.0-RELEASE is out.  (right now, we want to
> minimise differences between main and releng/15.0 for release.)
>
> [0] dist sets will still be supported for downstream consumers, but they
> won't be an installation option for FreeBSD.
>