Date: Thu, 14 Aug 2025 18:42:36 -0500 From: Kyle Evans <kevans@FreeBSD.org> To: freebsd-pkgbase@freebsd.org Subject: Re: Note: libutil.so bump from main-n279246-0c381b7f0570 Message-ID: <59f4cf31-12f5-44c4-b871-453cedda932f@FreeBSD.org> 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 8/14/25 16:20, Dag-Erling Smørgrav 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. > I have some WIP to make it configurable per-repository so that we can enable it by default only for pkgbase repositories to avoid too much of a disruption. IMO a prerequisite to enabling it by default is also making the pkg it archives them into configurable (and per-repo), so that we can maintain a clean separation between base-archived-libs and ports-archived-libs if both end up enabled. markj also noted that the pkg solver has a little bit of a flaw here, in that it doesn't take into account BACKUP_LIBRARIES when it develops its plan. The local pkg-removal-oops could've been mitigated with it if pkg would have counted its backup to another package as maintaining the shlib dependency. Resolving that wouldn't be strictly necessary, though. Thanks, Kyle Evanshome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?59f4cf31-12f5-44c4-b871-453cedda932f>