From Newsgroup: muc.lists.freebsd.stable

Colin Percival <cperciva_at_tarsnap.com> wrote on
Date: Thu, 16 Oct 2025 18:04:51 UTC :

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. 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.

One thing I'll note about having a mix of enabled and
disabled repositories, with both types having installed
packages: pkg version is always going to classify some
of the installed packages as orphaned. For reference:
# pkg version -r REPONAME . . .
classifies everything installed from some other repository
as orphaned, no matter if that repository is enabled or
not.
For a pkgbase context with FreeBSD-base not enabled . . .
# pkg version . . .
(no REPONAME) will classify everything installed from
FreeBSD-base as orphaned because it is not enabled.
===
Mark Millard
marklmi at yahoo.com
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.stable

On Oct 19, 2025, at 15:00, Mark Millard <marklmi@yahoo.com> wrote:

Colin Percival <cperciva_at_tarsnap.com> wrote on
Date: Thu, 16 Oct 2025 18:04:51 UTC :

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. 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.

One thing I'll note about having a mix of enabled and
disabled repositories, with both types having installed
packages: pkg version is always going to classify some
of the installed packages as orphaned. For reference:

# pkg version -r REPONAME . . .

classifies everything installed from some other repository
as orphaned, no matter if that repository is enabled or
not.

For a pkgbase context with FreeBSD-base not enabled . . .

# pkg version . . .

(no REPONAME) will classify everything installed from
FreeBSD-base as orphaned because it is not enabled.

Turns out that pkg fetch will only fetch from enabled
repositories. (This is consistent with the wording of
the pkg-fetch man page.) So, with FreeBSD-base not
enabled,
# pkg fetch -r FreeBSD-base . . .
would not fetch anything.
The man pages for pkg version and pkg fetch might need
some explicit notes about such overall consequences.
===
Mark Millard
marklmi at yahoo.com
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2