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

From: vermaden <vermaden_at_interia.pl>
Date: Wed, 20 Aug 2025 12:30:58 UTC 
Temat: Re: RFC: Renaming "FreeBSD" repo in /etc/pkg/FreeBSD.conf to "FreeBSD-ports"
Data: 2025-08-20 11:48
Nadawca: "Matteo Riondato" &lt;matteo@FreeBSD.org>
Adresat: "Dag-Erling Smørgrav" &lt;des@FreeBSD.org>; 
DW: "Miroslav Lachman" &lt;000.fbsd@quip.cz>; "Colin Percival" &lt;cperciva@freebsd.org>; "Mark Millard" &lt;marklmi@yahoo.com>; "FreeBSD Current" &lt;freebsd-current@freebsd.org>; "FreeBSD Mailing List" &lt;freebsd-ports@freebsd.org>; 

> 
> > 
>> On Aug 20, 2025, at 5:33 AM, Dag-Erling Smørgrav 
wrote:
>> 
>> Miroslav Lachman &lt;000.fbsd@quip.cz> writes:
>>> If there is one file for each repository, it can be managed using
>>> simple tools such as cp / rm / sed to enable, disable or modify
>>> repositories - good for scripted setups and automation.
>> 
>> The correct way to disable one of these repositories is to add
>> 
>>    repository-name: { enabled: false }
>> 
>> in a file in /usr/local/etc/pkg/repos.
> 
> It’s unclear (to me) whether that’s the *correct* way, or the
*recommended* way (pkg(8) calls it “a common idiom”), and in either
case *why* is that the recommended/correct way: what breaks if one modifies
/etc/FreeBSD.conf ? Why does it break?
> 
> It feels very unnatural to me to have one file in /etc specifying a
setting (enabled: true”), and another file in /usr/local/etc specifying
the opposite.
> 
> Also, it seems that whether having “repository-name: { enabled:
false}” would actually disable respository-name  would depend on the
order of directories in the configuration variable REPOS_DIR. This feels
quite brittle.
> 
> Thanks,
> Matteo

I would even ask broader question ... as pkg(8) is for third party packages and before PKGBASE had nothing to do with FreeBSD Base System - why someone thought about putting that config into /etc/pkg in the first place? :)

As pkg(8) kept all the software - well most of it as there is also /boot/modules - but still - inside /usr/local prefix - why it was not always the default good idea to keep it under /usr/local/etc/pkg since day one?

The pkg(8) tool needs to be bootstrapped anyway ... and config is very short and simple that even pkg(8) command can generate it on the fly during bootstrap..

... and yes - having separate files - one per repository is a +1 form my side.

Regards,
vermaden