Date: Sun, 08 Oct 2023 10:12:41 +0000 From: bugzilla-noreply@freebsd.org To: multimedia@FreeBSD.org Subject: [Bug 268652] Qt5: Some apps fails to start after upgrading to 5.15.8 Message-ID: <bug-268652-12827-8n67kOj0Ms@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-268652-12827@https.bugs.freebsd.org/bugzilla/> References: <bug-268652-12827@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D268652 --- Comment #73 from Tomoaki AOKI <junchoon@dec.sakura.ne.jp> --- (In reply to Tatsuki Makino from comment #71) Of course. :-) But in (hopefully) some rare cases, delete-from-ports softwares are mandato= ry. For those cases, Old libraries which are mandatory (new one does not work f= or them) and forced to be kept in /usr/local/lib/compat/pkg. We can lock installed ports, but it is not desirable not to update common libraries for some old locked ports. It would be nice if there is any efficient tool to delete only really safe = to delete libraries from /usr/local/lib/compat/pkg. FYI: pkg_replace basically works as oldest port upgrading tool, portupgrade. It keeps old libraries into /usr/local/lib/compat/pkg by default, unlike portmaster. This behaviour helps using applications in half-done state, some of requir= ed libraries are updated but others are not yet, for example, build failures. Default of portmaster would be focus on security. But it assumes that... *All ports are ALWAYS BUILT AND RUN SUCCESSFULLY, unless marked as BROKE= N. *ALL ports works 100% fine with old and updated ports. that is not at all realistic assumption. portupgrade was much more realist= ic. Unfortunately, portupgrade[-devel] is not well maintained for years, so pkg_replace popped in and maintained well by current maintainer. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-268652-12827-8n67kOj0Ms>