Re: RFC: Renaming "FreeBSD" repo in /etc/pkg/FreeBSD.conf to "FreeBSD-ports"

On 8/19/25 17:44, Mark Millard wrote:
> On Aug 19, 2025, at 17:25, Colin Percival <cperciva@freebsd.org> wrote:
>> Right, I don't see any reason for having separate files.  If I thought people
>> might want to delete one of them (e.g. rm /etc/pkg/FreeBSD-base.conf in order
>> to disable pkgbase) then I would separate them; but the recommended way to
>> disable a repository is with an {enabled: no} in /usr/local/etc/pkg/ so I
>> don't see any need to separate these.
> 
> Will a pkgbase repo be present and enabled by default?
> present but disabled? Not present at all in
> /etc/pkg/FreeBSD.conf ?
> 
> (I'm not trying to specify spelling for such here. But your
> note might be better with this intended spelling also
> being explicit so how it all fits together is more
> clear.)
> 
> If /etc/pkg/FreeBSD.conf is intended not to be edited at all
> by default, that might have implications for some default
> content there or inside /usr/local/etc/pkg/repos/ someplace
> if pkgbase is not enabled by default.
> 
> (My understanding is that pkgbase is off by default.)

pkgbase is off by default in 14 but will be on by default in 15.  People will
need it to update their systems for security updates, for example, since
freebsd-update is going away (at least in its present form -- it might turn
into a wrapper around pkg).

Users who want to update the base system from another source (no pun intended)
will need to configure their systems appropriately.

-- 
Colin Percival
FreeBSD Release Engineering Lead & EC2 platform maintainer
Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid