Page MenuHomeFreeBSD

release/tools: use pkg settings in /etc/pkg/FreeBSD.conf in containers
ClosedPublic

Authored by dch on Dec 5 2025, 5:44 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Feb 10, 4:08 PM
Unknown Object (File)
Sat, Jan 31, 3:04 PM
Unknown Object (File)
Thu, Jan 29, 4:14 PM
Unknown Object (File)
Thu, Jan 29, 2:03 PM
Unknown Object (File)
Wed, Jan 28, 12:16 PM
Unknown Object (File)
Sun, Jan 25, 9:09 PM
Unknown Object (File)
Sat, Jan 24, 10:00 PM
Unknown Object (File)
Wed, Jan 21, 5:47 PM
Subscribers

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

dch requested review of this revision.Dec 5 2025, 5:44 PM

The FreeBSD-base url here needs to have the pkg+: prefix otherwise it doesn't work in our new CDN world. It seems simplest to just enable here, and let /etc/pkg/FreeBSD.conf specify everything else.

I don't know what the correct path for the file should be, but it seems using the same as /etc/pkg/FreeBSD.conf seems the least confusing.

This is what we advise users to do in that file:

# To disable a repository, instead of modifying or removing this file,
# create a /usr/local/etc/pkg/repos/FreeBSD.conf file, e.g.:
#
#   mkdir -p /usr/local/etc/pkg/repos
#   echo "FreeBSD-ports: { enabled: no }" > /usr/local/etc/pkg/repos/FreeBSD.conf
#   echo "FreeBSD-ports-kmods: { enabled: no }" >> /usr/local/etc/pkg/repos/FreeBSD.conf
#
# Note that the FreeBSD-base repository is disabled by default.
...

i'm not familiar enough with the OCI build to review this, but the change looks right: we shouldn't be duplicating information that's already in /etc/pkg/FreeBSD.conf. this would also fix downstream users (like me) who ship a modified FreeBSD.conf.

Looks good to me, thanks Dave!

This revision is now accepted and ready to land.Dec 9 2025, 4:05 PM