From owner-freebsd-ports@freebsd.org Tue Dec 8 17:53:43 2015 Return-Path: Delivered-To: freebsd-ports@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 C05169D48DB; Tue, 8 Dec 2015 17:53:43 +0000 (UTC) (envelope-from crodr001@gmail.com) Received: from mail-ig0-x22a.google.com (mail-ig0-x22a.google.com [IPv6:2607:f8b0:4001:c05::22a]) (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 910691F1B; Tue, 8 Dec 2015 17:53:43 +0000 (UTC) (envelope-from crodr001@gmail.com) Received: by igvg19 with SMTP id g19so106630871igv.1; Tue, 08 Dec 2015 09:53:43 -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=g+7AoZcpfxC7wuvMkNX5PMbdElYfetAUqM4MtKz8mAA=; b=yUpwlGiTMADfqMEoVm64Kc4/P+DsKn+q8+TGzClyeVrXo2rWDZqUcY49FwBhCq5vGQ UjakTdZ6cfjKUjI6uyr46uXmNkJgchcYycPHphg58AwlzcCvovaE4GY2iJCtQ55vWWSV Auxu4HRwoRfCuUV5JV6aUtjtESlqHTOmRriyWg8Dw7+cZGN32MMqmT9OVQZpgntNkbiI 3aMMgtjHNxX0oU3cNE4Fkh36qA1Mozwb3XI3LOl5Q7q75LLmTVmNQk7lwYvpM4zrKUuV oH51mH3P4SAdCLG2uVjszUkMlxxFpxkBd57wAo7CmXuuDbMnF/DIGJw9oMMrqwk3JMri B88Q== MIME-Version: 1.0 X-Received: by 10.50.112.234 with SMTP id it10mr20528086igb.86.1449597222927; Tue, 08 Dec 2015 09:53:42 -0800 (PST) Sender: crodr001@gmail.com Received: by 10.50.152.69 with HTTP; Tue, 8 Dec 2015 09:53:42 -0800 (PST) In-Reply-To: <56624F9B.30508@FreeBSD.org> References: <56624F9B.30508@FreeBSD.org> Date: Tue, 8 Dec 2015 09:53:42 -0800 X-Google-Sender-Auth: E9L7nsLbLq6ZwRqmsomuS2CsvDc 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-ports@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Dec 2015 17:53:43 -0000 On Fri, Dec 4, 2015 at 6:44 PM, Kubilay Kocak wrote: > On 5/12/2015 9:40 AM, Craig Rodrigues wrote: > > 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 > > Short-term, swig20 could provide a symlink to the versioned binary until > a 'more correct' and permanent fix can be made. > > I'm not sure what to do about those ports that depend on swig30 in the > presence of swig20 also being installed, given they don't appear to > CONFLICT_INSTALL on each other. They both can't provide the swig > symlink. Supporting swig in DEFAULT_VERSIONS doesn't sound right and is > probably overkill. > > Actually, fixing the swig port in this way with a symlink is not a bad idea at all. I've looked at multiple platforms (Linux, OS X, Windows) and they all install a binary "swig". Pushing an upstream fix to Python distutils just to appease FreeBSD may not work out. The down side of this change would be that you would not be able to install swig1, swig2, and swig3 at the same time, but that might be OK. -- Craig