New packages: ipsvd, socklog-ucspi

[ghost]

cc: @leahneukirchen (socklog's maintainer)

Closes #41300.

socklog-ucspi

Testing the changes

• I tested the changes in this PR: briefly

ipsvd

The build method is not much different from socklog (the same author).

Testing the changes

• I tested the changes in this PR: briefly

New package

• This new package conforms to the package requirements: YES

[leahneukirchen]

Packaging ipsvd is fine, I'd not change the depends for socklog as this is a mode that's rarely used.

[leahneukirchen]

You could make a socklog-remote or so package that depends on socklog and ipsvd and provides a service.

[sbromberger]

Packaging ipsvd is fine, I'd not change the depends for socklog as this is a mode that's rarely used.

The problem is that the current installation of socklog is broken precisely because it assumes tcpsvd is available, and it's not. As I see it, the options are either

1. package ipsvd and make it a dependency,
2. change socklog dependency to include djb's ucspi-tcp package (might also need tcp6) and change the syntax in the socklog-ucspi run file,
3. disable / remove socklog-ucspi, and/or
4. modify the manpage to clarify that it won't work unless you install and configure a valid tcpserver implementation separate from the official manpage guidelines.

[ghost]

change socklog dependency to include djb's ucspi-tcp package (might also need tcp6) and change the syntax in the socklog-ucspi run file

socklog-conf.c and the manual page should be patched for this purpose.

I doubt this will be accepted here.

disable / remove socklog-ucspi

I believe you assume removal of the feature. See above.

modify the manpage to clarify that it won't work [...]

It would be nice to inform a user of tcpsvd coming with a separate package, but Void Linux is not the open based operating system with documentation stored in manual pages, meaning that void-specific documentation is handled in a different way (see void-docs).

Maybe it will be accepted at least there.

[leahneukirchen]

Void depends are only for essential dependencies, if you configure socklog to use tcpsvd, it's your problem to have the appropriate tools installed.

(My suggestion was to actually add a preconfigured setup to the socklog-ucspi package, however.)

[sbromberger]

Void depends are only for essential dependencies, if you configure socklog to use tcpsvd, it's your problem to have the appropriate tools installed.

Interesting. I hadn't thought of it this way before. In this case perhaps it's better to not create a runfile that is broken by default? If the user has to go through the steps of installing tcpsvd, then s/he is probably adept enough to create an appropriate service.

[ghost]

add a preconfigured setup to the socklog-ucspi package

I had my doubts for this new metapackage, but it seems I completely misunderstood your suggestion.