From owner-freebsd-ports-bugs@freebsd.org Mon Jan 4 13:02:03 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 BB364A608B2 for ; Mon, 4 Jan 2016 13:02:03 +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 ABCCE1423 for ; Mon, 4 Jan 2016 13:02:03 +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 u04D23oN049241 for ; Mon, 4 Jan 2016 13:02:03 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: Mon, 04 Jan 2016 13:02:03 +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: Mon, 04 Jan 2016 13:02:03 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D205852 --- Comment #5 from Mikhail Teterin --- (In reply to Antoine Brodin from comment #4) > Something like this may work for both sqlalchemy and sqlalchemy08 > (but the package builders will keep using sqlalchemy): Yes, that's an alternative -- for the particular case of sqlalchemy. But something more comprehensive may be in order. So far we've been resolving s= uch cases with USES-foo, but it may not be warranted in all cases. > There may be side effects of overwriting PKG_INFO Globally? Yes. Certainly a full test-run would be needed... --=20 You are receiving this mail because: You are on the CC list for the bug.=