Re: Is the base set of packages everything, or not?

A big picture.

FreeBSD = everything except FreeBSD. This era is expected to end in 2028.

Last month marked the beginning of the end of the era of vagueness and 
contradiction. The three repos, now (for FreeBSD 15 and 16):

FreeBSD-base
FreeBSD-ports
FreeBSD-ports-kmods


The FreeBSD base system is definitely a combination (collection) of two 
things: kernel, userland.

FreeBSD-base is understandable.

A base that might be customised, and maybe have ports or whatever on 
top. FreeBSD-base, FreeBSD-ports.

I suspect that when pkgbase was first envisaged, there was no intention 
to exclude all optional components of FreeBSD: 
<http://archive.today/2025.09.24-012809/https://docs.freebsd.org/en/books/handbook/bsdinstall/#bsdinstall-config-components>.

Whenever I write about non-base packages, no-one questions the meaning. 
It's understandable.

The emerging word cloud is something like this:

(base) (non-base) (subset) (set) (superset) (pkg) (sub package) 
(package) (super package) (meta package) (FreeBSD) (FreeBSD-base) 
(FreeBSD-ports) (FreeBSD-ports-kmods) (FreeBSD-set-base)

– and FreeBSD-base can be everything and the set a.k.a. meta package 
with the corresponding name (base) is definitely not everything and for 
13 and 14 FreeBSD is for everything except FreeBSD. What could possibly 
go wrong? ;-)

The droplets within a cloud can be documented in any number of ways, but 
(regardless of documentation) understanding will be easier if naming of 
each droplet can be fairly free from vagueness and contradiction.

----

Re: <https://reviews.freebsd.org/D52621#1203868>

Please, what is comp? ("… comp.txz as a separate set like NetBSD …")

I guess, complete 
(<https://www.startpage.com/do/dsearch?query=NetBSD+"comp.txz"&cat=web> 
finds only one thing).