Date: Wed, 2 Mar 2016 12:57:11 +1100 From: Kubilay Kocak <koobs@FreeBSD.org> To: Chris Inacio <nacho319@gmail.com>, freebsd-ports@freebsd.org Subject: Re: library porting question - optional python bindings Message-ID: <66498ca1-8d3d-27b6-e035-bbb1ab24d556@FreeBSD.org> In-Reply-To: <CAG_PEeyLw_VS=pL-3J6NZycx9-b_qo9GRaxoeV34i5gq_Cx=bg@mail.gmail.com> References: <CAG_PEeyLw_VS=pL-3J6NZycx9-b_qo9GRaxoeV34i5gq_Cx=bg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1/03/2016 1:38 PM, Chris Inacio wrote: > All, > > I'm trying to build a port definition for a library/application that can > optionally include Python bindings. The library/application generally > depends on other C libraries to exist (ZMQ v3, Protobufs-C) and if you > enable Python support, then you need a Python interpreter plus > Python-protobufs & python zmq. > > Putting an OPTION of Python in the port file is easy. Including the > optional Python dependencies (and presumably targets - but I'm not that far > yet) seems to be a lot more complicated. I haven't found anything that > would tell me how I'm supposed to do that. I have found that I'm supposed > to add pyXX prefixes to the python targets. > > Does anyone know of a similar application/library that I can go look at? > Is there any documentation on how to solve this? Package it separately if it: * Is listed on PyPI (.python.org) * Has value separate from the 'parent software' (on its own) * Users might want it without the parent software * Is pure python, OR * Doesn't otherwise explicitly require depend on the parent software >From the description above, given the dependencies of each of the software components are different (main software, python package), I'd go for separate packaging unless there's a good reason not to. > thanks, > Chris Inacio
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?66498ca1-8d3d-27b6-e035-bbb1ab24d556>