From owner-freebsd-python@freebsd.org  Wed Jan 13 11:55:38 2016
Return-Path: <owner-freebsd-python@freebsd.org>
Delivered-To: freebsd-python@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 ECAAFA803C8
 for <freebsd-python@mailman.ysv.freebsd.org>;
 Wed, 13 Jan 2016 11:55:37 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org
 [IPv6:2001:1900:2254:206a::50:5])
 by mx1.freebsd.org (Postfix) with ESMTP id D7DFA107F
 for <freebsd-python@freebsd.org>; Wed, 13 Jan 2016 11:55:37 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: by mailman.ysv.freebsd.org (Postfix)
 id D4FAEA803C7; Wed, 13 Jan 2016 11:55:37 +0000 (UTC)
Delivered-To: python@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 D49AEA803C6
 for <python@mailman.ysv.freebsd.org>; Wed, 13 Jan 2016 11:55:37 +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 AD21B107C
 for <python@FreeBSD.org>; Wed, 13 Jan 2016 11:55:37 +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 u0DBtbkA014907
 for <python@FreeBSD.org>; Wed, 13 Jan 2016 11:55:37 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: python@FreeBSD.org
Subject: [Bug 206194] lang/python27 install fails if misc/compat6x is
 installed [due to libreadline check]
Date: Wed, 13 Jan 2016 11:55:37 +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
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: 
Message-ID: <bug-206194-21822-ILNLLurOW2@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-206194-21822@https.bugs.freebsd.org/bugzilla/>
References: <bug-206194-21822@https.bugs.freebsd.org/bugzilla/>
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-python@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: FreeBSD-specific Python issues <freebsd-python.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-python>, 
 <mailto:freebsd-python-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-python/>
List-Post: <mailto:freebsd-python@freebsd.org>
List-Help: <mailto:freebsd-python-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-python>,
 <mailto:freebsd-python-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jan 2016 11:55:38 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206194

--- Comment #1 from Kubilay Kocak <koobs@FreeBSD.org> ---
This is interesting. I'll pose some questions (somewhat rhetorically) to he=
lp
us determine if, how and where this issue might be best addressed.

* If compatNx is installed, does that mean the user *always* wants or expec=
ts
*everything* thing to link against compat libraries? There is a user answer=
 to
this question and potentially a ports framework answer, which may be differ=
ent.

* Given the current description of the problem, I would expect *many* ports=
 to
be incorrectly linking against or not finding the expected compat libraries=
, in
this case libreadline via USES. Do we know of any other cases that: a) Fail=
 in
a similar way (not found, whether they fail to package or not), b) Fail in
other ways (linking to different library than expected)

* How will readline.mk decide when to depend on compatNx libraries, rather =
than
either existing base ones, or ones from ports, and on what basis and level =
of
granularity.


* Does, and if so how is this addressed for other libraries provided in
compatNx's that have ports framework and individual port implications?

* What is/are the actual 'root' cause(s) here?=20

lang/python27 is implicated only in so far as it doesn't check whether cert=
ain
C extensions compiled or not, before adding them to the plist. This 'could'=
 be
fixed. This is a fairly common type of failure across many ports, whether by
virtue of a compile failure, or an OPTION.

USES=3Dreadline is implicated only in so far as it does not detect the pres=
ence
of compatNx readline library and provide the necessary *FLAGS to find it.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=