Date: Thu, 14 Aug 2025 14:59:29 -0700 From: Mark Millard <marklmi@yahoo.com> To: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@FreeBSD.org> Cc: John Kennedy <warlock@phouka.net>, FreeBSD Current <freebsd-current@freebsd.org>, FreeBSD-pkgbase@freebsd.org Subject: Re: Note: libutil.so bump from main-n279246-0c381b7f0570 Message-ID: <D264EC7B-955C-44A0-BB8E-3AC2AFA6809D@yahoo.com> In-Reply-To: <86ms81vbuv.fsf@ltc.des.dev> References: <F4F162E8-8EB7-49F1-AA86-F238B1AB53BD@yahoo.com> <86ms81vbuv.fsf@ltc.des.dev>
index | next in thread | previous in thread | raw e-mail
On Aug 14, 2025, at 14:20, Dag-Erling Smørgrav <des@FreeBSD.org> wrote: > Mark Millard <marklmi@yahoo.com> writes: >> pkgbase updates do not have a "delete-old-libs" like >> step to do later as far as I know. The old libraries >> were not preserved. > > See BACKUP_LIBRARIES in pkg.conf(5). We should consider making it the > default. On the amd64 system I've long had: # grep BACKUP /usr/local/etc/pkg.conf BACKUP_LIBRARIES=true On the aarch64 system I've long had: # grep BACKUP /usr/local/etc/pkg.conf BACKUP_LIBRARIES=true I still ended up without the 3 libraries in each context: libutil.so.9 libcrypto.so.30 libssl.so.30 But there might be a distinction for such if 'pkg install' is used to progress instead of using 'pkg upgrade'? If it had left in place the 3 older files, there is still the question of the standard way of later cleaning out the old versions: no delete-old-libs === Mark Millard marklmi at yahoo.comhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D264EC7B-955C-44A0-BB8E-3AC2AFA6809D>