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

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

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

> On Fri, May 16, 2025 at 02:15:04PM +0200, Martin Husemann wrote:
>> I'll test the build w/o python and see what it saves. Adding a default-on
>> option for python support is another way to solve the issue (but build options
>> are lame).
>
> Since the build of python failed for me and fixing that will take longer
> I went for a simple solution and in retrospect this is probably a good-enough
> way forward: if using binary pkgs I wouldn't care for the addition python
> client stuff (taking minimal disk space) and for the affected machines
> (in my case things like sh3, mips, armv4, vax) I will have to do local
> builds anyway - so a build option solves my issue and is quite non-intrusive.
>
> Patch below, tested only for the 
>
> 	PKG_OPTIONS.ups-nut     += -python -openssl
>
> case.

I understand and agree with the "split packages are better than options"
sentiment.  However it's also true that they are harder, and I concur
that this approach is an improvement for many with no real negatives.

If you test it with default options and it's ok, I'm fine with you
committing it.  Doesn't need to be on a tiny machine of course.  If
that's really awkward I can queue doing it, but I have an unrelated
change in progress and also a micro update to do.

(As a nit, I'd put python first in suggested because PKG_SUPPORTED
precedes GROUPS, but that's style and not important.)

(I'm certainly open to contemplate further splitting if someone wants to
do the work.)