https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=300806
--- Comment #2 from Michael Osipov <[email protected]> --- I have a few questions: * Does the daemon run in-memory only? If so can it run as nobody? * Since this is network software, why isn't the python port not in net/ like others? * The sdist should be downloaded from PYPI like we do with other ports * Instead of python:3.11-3.15 why not remove the bound since we don'T have anything below 3.11 and 3.16 is still far away?! * Since you modified PEP517_BUILD_CMD will PEP517_INSTALL_CMD find the wheel in dist/? * USE_RC_SUBR= lockd_daemon: _daemon seems redundant since it is already lock*d* * net/lockd: I wouldn't add PYTHON option at all, we have a port which is built out of band. No benefit here. * net/lockd: TESTS: What is the benefit of installing the test executable? * +# lockd_daemon_interface="127.0.0.1" vs. ${lockd_daemon_interface:="localhost"}. This is a contradiction * lockd_daemon_flags aren't passed to the command at all * --interface: This is confusing you pass a hostname/IP address, but not an interface like igb0 or bge0. Can you clarify? Is the option misnamed? shouldn't it rather be --host? * lockd_daemon_prestart: You can do this in the post-install target and mark them @dir in the pkg-plist. See other ports. * Do I understand correctly that lockd will do a privilege drop by itself? * What is the difference between liblockd.so and liblockd_dll.so? -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
