>(1) > Keep pkg(8) for third party packages with /etc/pkg and /usr/local/etc/pkg and /var/db/pkg dirs for configuration. > > Use separate pkgbase(8) with /etc/pkgbase and /usr/local/etc/pkgbase and /var/db/pkgbase dirs for managing PKGBASE packages. By pkgbase(8) I have the same pkg(8) project in mind - just renamed as pkgbase(8) and with */pkgbase dirs instead of */pkg.
I can imagine a situation where a third-party package depends on a package from the base system. When you bootstrap a jail or your machine, you might start with a minimal installation, but I would expect pkg to automatically figure out what needs to be installed when it's required. On Mon, 4 Aug 2025 at 08:37, Don Lewis <truck...@freebsd.org> wrote: > On 3 Aug, Daniel Morante wrote: > > I just took a look at > > https://pkg.freebsd.org/FreeBSD:15:amd64/base_latest/ > > <https://pkg.freebsd.org/FreeBSD:15:amd64/base_latest/> and I am > > instantly disappointed. I was a fan of the idea, but seeing how they > > decided to make one package for each item is a massive bummer. Why would > > you split it up this way? When when you install the Mozilla Firefox via > > package, you don't install every file individually as a separate package. > > > > It's the same concept for FreeBSD. All these files make up a single > > entity "FreeBSD" the operating system. Why on earth would you install > > each item that's required to run FreeBSD as a separate package? All this > > will do is create increased overhead when installing the system (as each > > package must go through it's verification and transaction process), and > > all sorts of trouble down the line when dependency hell sets in. > > > > This is not the FreeBSD way. Very sad, concerned, and disappointed at > > this design choice. > > What benefit is there to installing setuid program lpr on an > appliance-like system without a printer other than enlarging the attack > surface? If I remove it, do I have to build my own freebsd-update > system to keep things up to date? > > I frequently want to build small systems without a compiler if I know > that I will never build software on them. > > >