From owner-freebsd-python@freebsd.org  Fri Dec  4 22:40:30 2015
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 E84CCA40193;
 Fri,  4 Dec 2015 22:40:30 +0000 (UTC)
 (envelope-from crodr001@gmail.com)
Received: from mail-ig0-x236.google.com (mail-ig0-x236.google.com
 [IPv6:2607:f8b0:4001:c05::236])
 (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 B7C5E1B5E;
 Fri,  4 Dec 2015 22:40:30 +0000 (UTC)
 (envelope-from crodr001@gmail.com)
Received: by igbxm8 with SMTP id xm8so47530438igb.1;
 Fri, 04 Dec 2015 14:40:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:sender:date:message-id:subject:from:to:content-type;
 bh=6mO7qm7izUZ28pvEN8dcHqELseDKKWtzA0JqFXpiCAk=;
 b=NfmtIP+3W1Njmq/pHbFvMof/Jqn8QKjBIrEiItL9ebopQ2vLofQycLsm1vwzkEnU+x
 4Xfecs1FhLx3vL8TGSVAAKzLaKmNHZEwAudp5jLAd+vMbVHmyly+TYuSz2yedq25ZIZ9
 CcJW2xPC+zVjWqQNg/FKb6S8gU6CSXtsoBCOaqheoLi08a7oqHDIt8BcU49iAdM+RoU/
 3OPqed/Xq0++uyCCzI/tP5pK6ZrNqdwed4ozsaqVVLBY0nCquV2fkSZYSCeLEitvMRaO
 O2gzbBiGnRd0Kakk9Ok04mNzbHrW9L37WL7RgZbYG5mYcxxqIb5lBMa7PcSzjT+/imyx
 kcuQ==
MIME-Version: 1.0
X-Received: by 10.50.155.106 with SMTP id vv10mr6138608igb.36.1449268830063;
 Fri, 04 Dec 2015 14:40:30 -0800 (PST)
Sender: crodr001@gmail.com
Received: by 10.50.152.69 with HTTP; Fri, 4 Dec 2015 14:40:30 -0800 (PST)
Date: Fri, 4 Dec 2015 14:40:30 -0800
X-Google-Sender-Auth: xYWZYUzNwnVHJ3egTC53RsYCCgo
Message-ID: <CAG=rPVc6AA37NFJkP+GaB6Y4BQP4aBYRLGGtQ6qc3VbmC38Qsg@mail.gmail.com>
Subject: Python and SWIG support in ports?
From: Craig Rodrigues <rodrigc@FreeBSD.org>
To: ports <freebsd-ports@freebsd.org>, 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 <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: Fri, 04 Dec 2015 22:40:31 -0000

Hi,

I am working with the upstream maintainer of M2Crypto (
https://gitlab.com/m2crypto/m2crypto ).

In the distutils that comes with Python, the swig binary is harcoded
to "swig" if on a POSIX system:

https://hg.python.org/cpython/file/v2.6.2/Lib/distutils/command/build_ext.py#l635

In our ports, we name our swig binaries things like
"/usr/local/bin/swig2.0" or
"/usr/local/bin/swig3.0".  How do we deal with this in Python ports which
use
SWIG?

If possible, I'd like to push a fix upstream for FreeBSD, if the upstream
maintainer
is OK with it.

Thanks.

--
Craig