Date: Thu, 20 Nov 2025 00:44:37 -0800 From: Mark Millard <marklmi@yahoo.com> To: grembo@freebsd.org, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: changing from pkgbase to regularbase Message-ID: <B528CAE4-2406-4ECE-B598-2ED8689B8977@yahoo.com> References: <B528CAE4-2406-4ECE-B598-2ED8689B8977.ref@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Michael Gmelin <grembo_at_freebsd.org> wrote on Date: Wed, 19 Nov 2025 16:25:20 UTC : > On Wed, 19 Nov 2025 16:14:27 +0000 > void <void@f-m.fm> wrote: > > > On Wed, Nov 19, 2025 at 03:14:28PM +0000, Minsoo Choo wrote: > > > > >Thanks for your effort! > > > > > >Since DESTDIR has been around for some time, I think the related > > >logic was accidentally removed while adopting pkgbase. This won't > > >take too much effort (just set DESTDIR to / if it is not specified), > > >and I don't need other information for now. > > > > I think I've found the reason for this > > in https://reviews.freebsd.org/D52879 which I didn't see before. > > > > There should be IMO a setting or a sysctl or something like > > pkgbase.enabled=0 though (my own perspective as a user) > > What is the procedure to run a custom kernel with pkgbase? Build and install a distinct kernel under a distinct name and have /boot/loader.conf set kernel="KNAME" (for example). That avoids updates messing each other up. Nothing says that you have to boot a kernel that pkgbase supplied. The old procedures work just fine for this, other than one issue: pkgbase uses /usr/src/ and usr/src/sys/ for its non-git source code directory trees. So, for git use, some other directory path should be used as the base for the git directory tree. Like the independent kernel, this independent directory tree avoids updates messing each other up as well. I'll note that for main and stable/15 , the pkgbase /usr/src/ and usr/src/sys/ need not match the same git commit --and the commit hashes involved are not published for reference that I know of. (But a kernel commit-hash prefix does show up in some uname output. There is no match to that for the world that I'm aware of.) > In the > last couple of years we needed stability patches (pf, zfs, etc.) on > almost every second release (at least temporarily, until an errata was > created). > > Would we need to run our own pkgbase server in this case or is there > another (non-hacky) way? === Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B528CAE4-2406-4ECE-B598-2ED8689B8977>