From owner-freebsd-ports-bugs@freebsd.org Tue Feb 2 17:37:56 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 230D4A985AB for ; Tue, 2 Feb 2016 17:37:56 +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 13DC0E68 for ; Tue, 2 Feb 2016 17:37:56 +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 u12HbtDf070291 for ; Tue, 2 Feb 2016 17:37:55 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:37:56 +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: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: mi@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: 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:37:56 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D205852 --- Comment #16 from Mikhail Teterin --- (In reply to Palle Girgensohn from comment #15) > OK. I would prefer we just had one sqlalchemy port, and bend the other > ports to work with the new fresh version only. I very strongly prefer that too, but it just is not always achievable -- to= day or in the future there may be a need to retain multiple versions of a port = in the tree because the latest version breaks compatibility for some of the consumers. Such a situation should not cause more damage than necessary, however, and a port that could use multiple versions of a dependency needs to be able to s= ay so -- instead of insisting on only one of the alternatives. --=20 You are receiving this mail because: You are on the CC list for the bug.=