From owner-freebsd-ports-bugs@freebsd.org Tue Feb 2 17:40:50 2016 Return-Path: Delivered-To: freebsd-ports-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 66CBBA98727 for ; Tue, 2 Feb 2016 17:40:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3D5D0F3D for ; Tue, 2 Feb 2016 17:40:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u12HenKo074606 for ; Tue, 2 Feb 2016 17:40:50 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 205852] Be nicer about multiple sqlalchemy ports Date: Tue, 02 Feb 2016 17:40:49 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Ports Framework X-Bugzilla-Version: Latest X-Bugzilla-Keywords: needs-qa, patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: koobs@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: portmgr@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc keywords Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Feb 2016 17:40:50 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D205852 Kubilay Kocak changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |koobs@FreeBSD.org, | |python@FreeBSD.org, | |robak@freebsd.org Keywords| |needs-qa --- Comment #17 from Kubilay Kocak --- (In reply to Palle Girgensohn from comment #15) I don't believe that's feasible. The reason why multiple versions exist because API compatibility changes between minor versions (perfectly ok), and consuming packages lag behind the latest major.minor until they have a chance to update. The pattern of creating a new fooXY and leaving dependent ports on their ol= der versions is because correctly, accurately and completely testing for not ju= st build time fixes, but correct runtime function (and/or regressions) is not something a sweeping change can achieve, and is best left to individual maintainers. Yes, maintainers should be encouraged to update the dependencies. Yes, if older versions are no longer supported, they should be DEPRECATED.= =20 Yes, if port upstreams have 'bumped' their sqlalchemy dependencies, the por= ts should follow suite. See Also: Upgrade databases/py-sqlalchemy https://reviews.freebsd.org/D908 Which is still open (CC'ing bartek@) This is a very similar problem space to our djangoXY ports, and deserves careful consideration. Also why is this a Ports Framework issue, when the changes are for two individual ports?=20 I believe this needs python@ too, and it would be beneficial if any solution applied to other instances where multiple fooXY and multiple consumers for = said ports exist, with ranged or limited dependency specifications. --=20 You are receiving this mail because: You are on the CC list for the bug.=