Re: separation of pkgbase from pkg (was: Re: FreeBSD pkgbase vs distsets.)
Benjamin Jacobs <[email protected]>
| Newsgroups | gmane.os.freebsd.devel.hackers |
|---|---|
| Message-ID | <20260223015019.46e9fd61@t14> |
On Fri, 20 Feb 2026 22:29:35 +0100 vermaden <[email protected]> wrote: > Hi, > > I tried to propose the same thing even before FreeBSD 15.0-RELEASE > was released here: > - > https://lists.freebsd.org/archives/freebsd-pkgbase/2025-July/000596.html > > To have pkgbase(8) command with separate configs/paths nad SQLite > database for Base System while leaving current pkg(8) with its own > paths and database for third party packages ... but there was no > interest. Hi, One of the problems with this approach is that it breaks the dependency that ports can have on a base package. This is an extremely useful feature allowing to install a really small set of base packages while having the confidence that any missing piece required by a port gets automatically installed. Personnaly I don't think that it would be a wise way forward. Mostly due to the increase in complexity, bug surface and chance of errors. If one wish to do that today, it is just a matter exporting a couple of environment variables. I've done it... and stopped for the reasons exposed ;-) Best regards, Benjamin P.S.: one thing that I seem to be missing with pkgbase is the creation of /boot/kernel.old when installing a new kernel (or maybe I just need to rtfm?)