On Sat, Sep 03, 2016 at 11:32:20AM +0100, Marius Bakke wrote: > Many distros prefix OpenBSD projects with ambigous names with > "openbsd-". E.g. "openbsd-netcat", "openbsd-ntpd" etc. We don't appear > to have that problem yet, but I think this could be a good precedent.
Is "openbsd-ntpd" the same thing as OpenNTPD? [0] As for openbsd-netcat, this was discussed on guix-devel recently, and we learned that OpenBSD does not provide a portable release of their netcat client. I don't think it would be appropriate for us to re-package Debian's unmaintained port of this software. [1] I looked at `apt-cache search openbsd`, which searches my Debian package cache for packages related to OpenBSD. I *think* that there isn't anything packaged with an "openbsd-" name that OpenBSD offers a portable release of, but I'm not sure about openbsd-inetd. On the other hand, they explicitly provide portable releases of things like OpenNTPD, OpenSSH, LibreSSL, and now acme-client. They really pushed the issue with this "acme-client". Maybe they should have kept the old name, letskencrypt, for the sake of all the GNU / Linux distros :) [0] http://www.openntpd.org/ [1] http://lists.gnu.org/archive/html/guix-devel/2016-07/msg00084.html
