Created attachment 154513 [details] httpd.shar FreeBSD port of OpenBSD http daemon http://chaosophia.net/poudriere/httpd-5.6.20150209-101x386.log http://chaosophia.net/poudriere/httpd-5.6.20150209-10x386.log http://chaosophia.net/poudriere/httpd-5.6.20150209-84x386.log http://chaosophia.net/poudriere/httpd-5.6.20150209-93x386.log http://chaosophia.net/poudriere/httpd-5.6.20150209-101x64.log http://chaosophia.net/poudriere/httpd-5.6.20150209-10x64.log http://chaosophia.net/poudriere/httpd-5.6.20150209-84x64.log http://chaosophia.net/poudriere/httpd-5.6.20150209-93x64.log
Wouldn't it make sense to consider renaming the binary to allow for an installation next to apache?
Created attachment 158542 [details] Updated httpd with alternative name to avoid Apache conflicts I have modified this port of OpenBSD's httpd service a little. This shar causes the executable file and manual pages to be installed as "openbsd-httpd" instead of just "httpd". I've also removed the "conflicts" flag from the Makefile. Something that should probably be done in the future is adding a sample configuration file to this port. There is an example config in the manual page, so it's not a pressing issue, but it would be nice to have a sample config.
(In reply to jsmith from comment #2) > Created attachment 158542 [details] > Updated httpd with alternative name to avoid Apache conflicts > > I have modified this port of OpenBSD's httpd service a little. This shar > causes the executable file and manual pages to be installed as > "openbsd-httpd" instead of just "httpd". I've also removed the "conflicts" > flag from the Makefile. > > Something that should probably be done in the future is adding a sample > configuration file to this port. There is an example config in the manual > page, so it's not a pressing issue, but it would be nice to have a sample > config. Not trying to hijack this port in any way. But I'd just like to suggest that "ohttpd" might be a nice alternative. It's easier to type too. :) Just saying...
/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 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
I'm not strongly in favour of one name or another, but I do wonder if shortening it so much is a good idea. I mean, let's assume a new user wants to install the OpenBSD httpd software, but they do not know if it is in the ports tree or what its name is. They go to freshports.org and start running searches. In my opinion, it seems likely they are going to search for "httpd", "openbsd" and maybe "openhttpd". Whatever name is decided on should probably be easy to find based on the above search terms. Will "obhttpd" appear in the top five search results for any of the above terms? Would "ohttpd"? I think that should be a factor in the naming choice. Sure, obhttpd is easy to type, but chances are a sysadmin will only type the name three or four times during the entire life of the server. I believe the port's name should be easy to find, perhaps more so than easy to type.
(In reply to jsmith from comment #6) > I'm not strongly in favour of one name or another, but I do wonder if > shortening it so much is a good idea. I mean, let's assume a new user wants > to install the OpenBSD httpd software, but they do not know if it is in the > ports tree or what its name is. They go to freshports.org and start running > searches. > > In my opinion, it seems likely they are going to search for "httpd", > "openbsd" and maybe "openhttpd". Whatever name is decided on should probably > be easy to find based on the above search terms. Will "obhttpd" appear in > the top five search results for any of the above terms? Would "ohttpd"? I > think that should be a factor in the naming choice. > > Sure, obhttpd is easy to type, but chances are a sysadmin will only type the > name three or four times during the entire life of the server. I believe the > port's name should be easy to find, perhaps more so than easy to type. Ahhh. I think I perhaps missed your earlier point(s). For the record; I am not suggesting that you change the name of the port itself. But rather, that you might want to consider changing the name of the _executable_. What you say is _quite_ true. The name of the port indeed _should_ reflect it's intended use, and origin. I completely agree. :) I hope my intention is now more clear. :) --Chris
Created attachment 163606 [details] httpd 5.7.20150508 - Update version to 5.7.20150508. - Rename binary and config file to obhttpd to avoid Apache conflicts - Remove conflict with apache port http://rein.chaosophia.net/poudriere/httpd-5.7.20150508-102x386.log.txt http://rein.chaosophia.net/poudriere/httpd-5.7.20150508-102x64.log.txt http://rein.chaosophia.net/poudriere/httpd-5.7.20150508-93x386.log.txt http://rein.chaosophia.net/poudriere/httpd-5.7.20150508-93x64.log.txt
A commit references this bug: Author: riggs Date: Sun Dec 6 12:17:52 UTC 2015 New revision: 403107 URL: https://svnweb.freebsd.org/changeset/ports/403107 Log: Add port of OpenBSD http daemon PR: 198705 Submitted by: koue@chaosophia.net (maintainer) Changes: head/www/Makefile head/www/httpd/ head/www/httpd/Makefile head/www/httpd/distinfo head/www/httpd/files/ head/www/httpd/files/obhttpd.in head/www/httpd/pkg-descr
A commit references this bug: Author: riggs Date: Sun Dec 6 15:41:37 UTC 2015 New revision: 403117 URL: https://svnweb.freebsd.org/changeset/ports/403117 Log: Move www/httpd to www/openhttpd to avoid consistency issues - Move to www/obhttpd - Avoid config file name conflict: httpd.conf -> obhttpd.conf PR: 198705 Changes: head/www/Makefile head/www/httpd/ head/www/obhttpd/ head/www/obhttpd/Makefile