Re: PKGBASE upgrade from ALPHAxx to BETAxx

On Oct 16, 2025, at 11:04, Colin Percival <cperciva@tarsnap.com> wrote:

> On 10/16/25 10:49, Patrick M. Hausen wrote:
>>> Am 16.10.2025 um 19:44 schrieb Mark Millard <marklmi@yahoo.com>:
>>> To my knowledge, /etc/pkg/ only has files that are expected to
>>> apply to all systems, no matter how installed/updated. Also,
>>> the files in /etc/pkg/ are expected to not be edited. The
>>> overriding text goes in files in /usr/local/etc/pkg/respos/
>>> instead. (Technically such are conventions, not requirements,
>>> but they fit with FreeBSD update processes in a particular way.)
>> I follow that argument.
>> But isn't pkgbase supposed to be the new normal starting with 15.0?
>> Sorry for the noise if I confused that. Then it will land in /etc/pkg/FreeBSD.conf in 16?
> 
> I'm planning on putting a "FreeBSD-base" repository configuration into
> /etc/pkg/FreeBSD.conf in 15.

Even for installs via "traditional distribution sets"? Or just for
"technology preview" installs?

> It will be disabled by default, in order
> to avoid "pkg delete -af" problems, but "pkg upgrade -r FreeBSD-base"
> should work out of the box.

Had I known such, various of my testing activities would
have been different.

Looks like commands that handle the explicit reference to
a disabled repository are documented as including:

/usr/local/share/man/man8/pkg-install.8.gz:                Install packages from only the named repository, irrespective
/usr/local/share/man/man8/pkg-rquery.8.gz:             irrespective of the configured “enabled” status from repo.conf.
/usr/local/share/man/man8/pkg-search.8.gz:                 irrespective of the configured “enabled” status from
/usr/local/share/man/man8/pkg-update.8.gz:            update only the named repository, irrespective of the configured
/usr/local/share/man/man8/pkg-upgrade.8.gz:                 Install packages from only the named repository, irrespective
/usr/local/share/man/man8/pkg-version.8.gz:                 the named repository only, irrespective of the configured

Later I'll do some exploration of that.

I'll note that "man pkg-fetch" does not say that it does such:

     -r reponame, --repository reponame
                   Fetches packages from the given reponame if multiple repo
                   support is enabled.  See pkg.conf(5).

> The reasons this hasn't happened yet have to do with release engineering
> processes and setting up the systems for building updates securely.


===
Mark Millard
marklmi at yahoo.com