From owner-freebsd-python@freebsd.org Wed Dec 9 01:15:19 2015 Return-Path: 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 53AF49B71A4; Wed, 9 Dec 2015 01:15:19 +0000 (UTC) (envelope-from crodr001@gmail.com) Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001:c06::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 26CEB1D3E; Wed, 9 Dec 2015 01:15:19 +0000 (UTC) (envelope-from crodr001@gmail.com) Received: by ioc74 with SMTP id 74so43302296ioc.2; Tue, 08 Dec 2015 17:15:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=xtVuV6OrBtnCiHEUNvxVj7qWdurmsvLjOXqUH54/EW4=; b=dNOd8ZEEd9rNmp8AXwJ5YhWfufFS9732aLvoyKYb3gNaYyUF1ETchhC2DqZeHfm2fO n/xmEPBohYECWhFxp95On+QxVCavt8OnyM8MOdLGH4b5sJnwZLTmU9B09Bh+5qfo7TS8 DBHLrn7JcRmjD+OD/Ll+QQxdZn/VlFxlX6Ib0PeNypgAQuXMV7yW12YFHfpO+ErBmM7D GSHQJSX9wI9LauXT9HZmZV2Jri/PzoLepYZOqdqY/Ssg5YTf8YnL60ymUy8gDhNMKPXO ag2gQRJKKDZFMsCdY9knQhpSJ0eZffXVBH4LnyLdsR/QBfVKnorGSHgMd+eb6va547As Gk3w== MIME-Version: 1.0 X-Received: by 10.107.11.23 with SMTP id v23mr3233122ioi.184.1449623718421; Tue, 08 Dec 2015 17:15:18 -0800 (PST) Sender: crodr001@gmail.com Received: by 10.50.152.69 with HTTP; Tue, 8 Dec 2015 17:15:18 -0800 (PST) In-Reply-To: <56677151.9050403@FreeBSD.org> References: <56624F9B.30508@FreeBSD.org> <56677151.9050403@FreeBSD.org> Date: Tue, 8 Dec 2015 17:15:18 -0800 X-Google-Sender-Auth: YAZ8XgOQOAOfBK1lLYN26gm4sSk Message-ID: Subject: Re: Python and SWIG support in ports? From: Craig Rodrigues To: "koobs@freebsd.org" Cc: ports , freebsd-python@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Dec 2015 01:15:19 -0000 On Tue, Dec 8, 2015 at 4:09 PM, Kubilay Kocak wrote: > The correct thing to do is be PEP-394'ish compatible (even though swig > itself isnt a python package). Again swig20 is a short term solution. > > I have no idea why you refered to PEP394. > The root cause is technically an inadequate 'find the binary file name' > method. > Probably, but pushing a change upstream to Python distutils just to appease FreeBSD might be hard. Unless you want to patch the distutils in all our our Python ports. > > We do want to keep/allow concurrent swig install support if they don't > already CONFLICT_INSTALL > Why? swig isn't used a lot. It is inconvenient, but not a big deal to install/uninstall different swig versions. -- Craig