Date: Wed, 20 Aug 2025 20:07:58 +0100 From: Graham Perrin <grahamperrin@gmail.com> To: freebsd-current@freebsd.org, freebsd-ports@freebsd.org Cc: FreeBSD Release Engineering Team <re@FreeBSD.org> Subject: Re: RFC: Renaming "FreeBSD" repo in /etc/pkg/FreeBSD.conf to "FreeBSD-ports" Message-ID: <cb439034-af16-43ee-9166-4cdd4cb50620@gmail.com> In-Reply-To: <5d2daa68-cd27-4a56-9d69-5453b588a086@freebsd.org>
index | next in thread | previous in thread | raw e-mail
On 19/08/2025 23:49, Colin Percival wrote: > … rename "FreeBSD-kmods" to "FreeBSD-ports-kmods". … I prefer FreeBSD-kmods. Not because FreeBSD-ports-kmods is troublesome, per se. Partly because: - it's only slightly more descriptive - the longer name is _not_ a hint that the repo is limited to a _subset_ of non-base kernel modules. Also partly because users have become accustomed to the distinctive existing name, and I'm not aware of any user suggesting an alternative. I think of FreeBSD-kmods as complementing both FreeBSD-base _and_ FreeBSD-ports. If you rename the repo to reflect only the origin of the packages: that's, like, only part of the picture.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cb439034-af16-43ee-9166-4cdd4cb50620>