Re: Split python client from sysutils/ups-nut ?

[Greg Troxel <gdt%lexort.com@localhost>]

Martin Husemann <martin%duskware.de@localhost> writes:

> The pkg sysutils/ups-nut includes support for a python extension (PyNUT) and
> a test for that part.
>
> I think it would be good to split out everything requiring python from
> this pkg into a separate (sysutils/ups-py-nut ?) pkg, even if the build
> system does not make that straightforward.
>
> Alternative: split out the client part (everything but upsd, the drivers
> and PyNUT) into a separate (sysutils/ups-nut-client?) package.

As $MAINTAINER, I haven't done this, because it solves a problem that I
don't have.

It's hard to know whether client vs upsd/drivers/pyNUT or
not-python/python is the best split.  It should be easy for you to build
nut from sources (or locally modify pkgsrc to disable python) and see
what the build times are.

I observe that snmp, cgi and usb are already split.    I haven't really
paid attention because I don't use any of those, but my impression is
that those split packages build everything and just install the needed bits.

(At this point I question the wisdom of splitting usb.  I have a UPS
with a real serial port, but I don't know anyone else that still does.)


Another option is to have python be an option, default on.