Date: Tue, 21 Jul 2015 14:18:42 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 198705] [new port] www/httpd: OpenBSD http daemon Message-ID: <bug-198705-13-ixXM6wXCLK@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-198705-13@https.bugs.freebsd.org/bugzilla/> References: <bug-198705-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198705 --- Comment #5 from Chris Hutchinson <portmaster@bsdforge.com> --- (In reply to Nikola Kolev from comment #4) > /usr/ports/mail/spamd uses obspamd as name because of spamassasin. obhttpd > is also an option. Changing binary name is simple and for me it is not > important what will be the name. > /usr/ports/www/xshttpd uses httpd and httpd.conf manual pages and it is in > conflict with the current port. Probably renaming the manual pages of the > current port? Edit manual pages to use new name convention? Suggestions? I > prefer minimal changes from the upstream. In the end, it should be what *you* want. You're the proposed maintainer. :) I only suggested ohttpd, because openbsd-httpd seemed unnecessarily long, and of course, httpd had already been taken (Apache). Maybe obhttpd should be the standard "convention" -- meaning ob = OpenBSD Fewer letters to fool with when making the necessary changes (binary/man pages). Honestly, I'm happy with whatever you choose. I only suggested ohttpd because it was close to what most people associate with an HTTPd server, and there are less letters to (mis)type. :) All the best to you. I'm looking forward to this getting into the ports tree. Thanks! --Chris -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-198705-13-ixXM6wXCLK>