Date: Tue, 19 Aug 2025 17:17:24 -0700 From: Mark Millard <marklmi@yahoo.com> To: Colin Percival <cperciva@freebsd.org>, 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: <05CD2AAD-31EA-471B-8028-A3902D7A4192@yahoo.com>
index | next in thread | raw e-mail
Colin Percival <cperciva_at_freebsd.org> wrote on
Date: Tue, 19 Aug 2025 22:49:23 UTC :
> Hi everyone,
>
> 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 ?
> To reduce long-term confusion, I'm intending to rename the "FreeBSD"
> repository to "FreeBSD-ports", and similarly rename "FreeBSD-kmods" to
> "FreeBSD-ports-kmods". The repositories will still work, and will still
> access the same URLs, but the change will be visible; probably the most
> common scenario where this would cause problems for users is if they have
> "FreeBSD: {enabled: no }" in /usr/local/etc/pkg/repos/FreeBSD.conf, since
> that would need to be adjusted to chase this change.
/usr/local/etc/pkg/repos/FreeBSD-ports.conf ?
> For obvious reasons, this change would not be MFCed.
>
> You've got a week to convince me that this is a bad idea, otherwise I'll
> make the change on the 27th; I want to get this out of the way before we
> get too close to branching stable/15.
The adjusted file naming would tend to suggest a separate file
for pkgbase content.
Naming left as it is might suggest all in one file, pkgbase
included.
===
Mark Millard
marklmi at yahoo.com
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?05CD2AAD-31EA-471B-8028-A3902D7A4192>