On Tue, Mar 1, 2016 at 8:57 PM, Kubilay Kocak <ko...@freebsd.org> wrote:
> 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 > > I don't believe you can build the Python package without the availability of the C library. _______________________________________________ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
