Date: Thu, 15 Mar 2018 18:00:12 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 226611] KDE4_GENERIC_LIB_VERSION set to expected, not factual Message-ID: <bug-226611-13-hAX4mj1REY@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-226611-13@https.bugs.freebsd.org/bugzilla/> References: <bug-226611-13@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=3D226611 --- Comment #2 from Mikhail Teterin <mi@FreeBSD.org> --- (In reply to Tobias C. Berner from comment #1) > We only support one kdelibs verison at a time. That makes sense -- and I do have exactly one kdelibs installed on my syste= m. It just is not the same version you have... > Is there a reason not to update? There may be a multitude of reasons for different people. The point is, the ports system should not create a new requirement. If a KDE-component is wil= ling to build against an earlier version of kdelibs, FreeBSD ports should not require me to upgrade just to add this component. Consider the following likely scenario: 1. User installs a certain minimal set of KDE ports. 2. kde@ team upgrades the KDE-ports. 3. User updates his ports collection and attempts to add a KDE-port, which = he did not have before. The upgrade of all of the already-installed KDE-ports must not be a require= ment for the step 3 to succeed. This is the same "debate" we've had years ago regarding LIB_DEPENDS -- when various ports insisted on requiring a particular major shlib number. Fortunately, that debate is behind us. Unfortunately, KDE-team needs a refresher... --=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-226611-13-hAX4mj1REY>