Date: Wed, 20 Aug 2025 06:19:48 -0400 From: Matteo Riondato <matteo@FreeBSD.org> To: Gleb Popov <arrowd@freebsd.org> Cc: FreeBSD Current <freebsd-current@freebsd.org>, FreeBSD Mailing List <freebsd-ports@freebsd.org> Subject: Re: RFC: Renaming "FreeBSD" repo in /etc/pkg/FreeBSD.conf to "FreeBSD-ports" Message-ID: <5C65983C-2D75-4250-AADD-12699A4CE252@FreeBSD.org> In-Reply-To: <CALH631=w4Uv%2BRBTkRX0UZG9ktV9whtjaxSSOcmLmKnx7ARafww@mail.gmail.com> References: <05CD2AAD-31EA-471B-8028-A3902D7A4192@yahoo.com> <5bece4af-0bec-457e-847f-7ca1cb031f86@freebsd.org> <590B86F2-6F9F-46BF-9569-03F72EA93B5D@FreeBSD.org> <91cccdac-406c-46dc-bdbe-c1c016cdee99@freebsd.org> <c7425732-2d2c-446d-9877-493070d24b90@quip.cz> <864iu2jq1a.fsf@ltc.des.dev> <051BA4A9-E45B-4CF5-95C5-B6F53948DB58@FreeBSD.org> <CALH631=w4Uv%2BRBTkRX0UZG9ktV9whtjaxSSOcmLmKnx7ARafww@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
> On Aug 20, 2025, at 6:15 AM, Gleb Popov <arrowd@freebsd.org> wrote:
>
> On Wed, Aug 20, 2025 at 12:48 PM Matteo Riondato <matteo@freebsd.org> wrote:
>>
>> 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?
>
> The /etc/pkg/FreeBSD.conf file comes from base (some pkgbase package
> or as a result of make installworld or something like that). This
> means that system upgrades must handle edits to this file somehow -
> either by overwriting your changes with vanilla version or by merging
> them, which can't be done 100% automatically.
This is true for so many files under /etc, and we have a solution with etcupdate (indeed, not 100% automatically, but widely accepted).
> So encouraging users to not touch system configs but rather write
> add-ons to these configs make upgrades less painful.
It seems to me that we don’t have this encouragement with any other files in /etc.
Why can’t etcupdate handle the changes/updates to FreeBSD.conf?
>> 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.
>
> This is also a very common problem which has an established solution
> by prefixing config files with numbers, like
> 10-disable-freebsd-repos.conf
No, REPOS_DIR is about _directories_, not files.
Thanks,
Matteo
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5C65983C-2D75-4250-AADD-12699A4CE252>