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

On Aug 19, 2025, at 17:51, Colin Percival <cperciva@freebsd.org> wrote:

> 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.

With 15 or main [then: 16] as the context . . .

Will buildworld buildkernel installkernel installworld (not
referencing various steps) for folks using source code based
updates need to undo an addition of pkgbase from the
installworld activity? Never? Just once? Each time?

Or is "on by default" more selective somehow for such
contexts?

Note: In my context I'll have pkgbase in use for the
booted world and available for use as the booted kernel,
although I'll have personal-build alternate kernels too.
My from-source installed world will be in, for example, a
chroot directory tree(s) and in a poudriere jail world(s).

I keep /usr/src/ for pkgbase to manage for itself and have
a separate /usr/main-src/ (as an example).

So I'll be dealing with both types of contexts no matter
what.

> 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.


===
Mark Millard
marklmi at yahoo.com