> On Aug 19, 2025, at 9:05 PM, Colin Percival <[email protected]> wrote: > > On 8/19/25 17:58, Matteo Riondato wrote: >>> On Aug 19, 2025, at 8:25 PM, Colin Percival <[email protected]> wrote: >>> On 8/19/25 17:17, Mark Millard wrote: >>>> Colin Percival <cperciva_at_freebsd.org> wrote: >>>>> With pkgbase being the intended way for users to manage 15.0 systems, >>>>> the current default /etc/pkg/FreeBSD.conf gives rise to confusion: It >>>>> defines a "FreeBSD" pkg repository which is in fact specifically bits >>>>> maintained *outside* of FreeBSD (and packaged via the ports tree). >>>> Not that I consider an appropriate answer obvious, but >>>> the file names as well as the content in the file? : >>>> /etc/pkg/FreeBSD-ports.conf ? >>> >>> I wasn't planning on changing the file name, no. >> Why is then this file named “FreeBSD.conf” ? > > Because it's the configuration file which describes pkg repositories provided > by the FreeBSD project?
I guess =) Maybe this was discussed in phabricator as you mentioned, but it would seem more natural to me to provide individual files for each repository provided by the project, with a descriptive name (e.g., FreeBSD-ports, FreeBSD-ports-kmod, …, and store them in /usr/local/etc/pkg/repos/ This solution would also allow to remove the (IMHO weird) suggestion of creating *another* file FreeBSD.conf in /usr/local/etc/pkg/repos to disable some of these repositories (why is that suggestion needed? Can’t etcupdate handle changes to /etc/pkg/FreeBSD.conf ?) Thanks, Matteo
