Re: None of "man freebsd-base" (or "man pkgbase"), "man pkg-upgrade", or "man pkg-install" deal with documenting .pkgsave and/or .pkgnew behavior or how to handle such

On 7/3/26 02:21, void wrote:
> On Tue, Jun 30, 2026 at 10:04:06AM -0700, Mark Millard wrote:
> 
>> Variations on:
>>
>> find -s / \
>>  \( -name \*.pkgnew -or -name \*.pkgsave -or -name .pkgtemp.\* \) \
>>  -exec ls -lodT {} \; \
>> | more
>>
>> can be of use.
> 
> I see some of these remnants on systems which have never had pkgbase.
> Some managed by freebsd-update, most not - they're running -stable.
> One is running -current.

The file types are not new with pkgbase. They have long existed for pkg
for port-packages without pkgbase as well. The generation of such files
is just comparatively rare for port-packages.

> 
> Like
> -rw-r--r--  1 root wheel - 786736 Oct 18 04:00:38 2020 /usr/local/etc/
> ssl/cert.pem.pkgsave
> -rw-r--r--  1 root wheel - 786736 Oct 18 04:00:38 2020 /usr/local/
> openssl/cert.pem.pkgsave
> 
> -rwxr-xr-x  1 root wheel - 28209496 Jul 13 02:15:14 2023 /usr/local/
> sbin/pkg-static.pkgsave

The pkgbase configuration files lead to no contributions to /usr/local/
by pkg as far as I know. Those are from pkg being used for port-packages
instead.

> 
> So there will be no 'man pkgbase' anyway.
> Are these files safe to delete?
> What is their purpose on a non-pkgbase system?
> 

I've no clue what your certificate criteria are for ssl and openssl. So
I've no clue if you might need a merge or not of those configuration
files --other than the dates going back to 2020 suggesting they are too
old to have the content be of interest.

/usr/local/sbin/pkg-static.pkgsave should just be an old 20023 version
of pkg-static from back in 2023. I'd be surprised if you need it.

-- 
===
Mark Millard
marklmi at yahoo.com