RFC: Renaming "FreeBSD" repo in /etc/pkg/FreeBSD.conf to "FreeBSD-ports"
- Reply: George Mitchell : "Re: RFC: Renaming "FreeBSD" repo in /etc/pkg/FreeBSD.conf to "FreeBSD-ports""
- Reply: Gleb Popov : "Re: RFC: Renaming "FreeBSD" repo in /etc/pkg/FreeBSD.conf to "FreeBSD-ports""
- Reply: Graham Perrin : "Re: RFC: Renaming "FreeBSD" repo in /etc/pkg/FreeBSD.conf to "FreeBSD-ports""
- Reply: Bakul Shah : "Re: RFC: Renaming "FreeBSD" repo in /etc/pkg/FreeBSD.conf to "FreeBSD-ports""
- Reply: Graham Perrin : "Re: RFC: Renaming "FreeBSD" repo in /etc/pkg/FreeBSD.conf to "FreeBSD-ports""
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
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). 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. 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. -- Colin Percival FreeBSD Release Engineering Lead & EC2 platform maintainer Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid