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

On Wed, Aug 20, 2025 at 10:19:48AM +0200, Miroslav Lachman wrote:
> ... I would like to have a separate file for each repository, similar to the
> contents of /etc/newsyslog.conf.d/ or /etc/syslog.d/.
> 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. However, if there are multiple
> repositories in one file, this task becomes much more complicated.

  In general, I like that approach.  I don't particularly care if *all* the
FreeBSD files are broken out, but I do like being able to have my own files
(like my private poudriere package repo) and I don't have to worry about
doing something that will mess with the FreeBSD-provided files and make
etcupdate's life more difficult.

  I do like being able to override the defaults set in other people's files
(disabling other repos so that the only thing available is my private one,
for example).

  Most of my bad experiences are with RedHat, who's default behavior is to
basically "this isn't exactly what I was expecting, don't stomp on the old
file, make a .rpmnew file and carry on."  I'm not sure how many issues are
caused by etcupdate conflicts in the big scheme of things, but for me they're
small and conflicts are rare enough.

  I'm particularly staring at that "scripted setups" scenario.  If I can
override defaults with my own files, I don't have to parse "their" files and
worry about their contents changing subtly over time.  "{ enabled: no }" in
a file I control is great.