Bug 198705 - [new port] www/httpd: OpenBSD http daemon
Summary: [new port] www/httpd: OpenBSD http daemon
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Thomas Zander
URL:
Keywords: feature, patch, patch-ready
Depends on:
Blocks:
 
Reported: 2015-03-19 13:45 UTC by Nikola Kolev
Modified: 2015-12-06 15:42 UTC (History)
3 users (show)

See Also:


Attachments
httpd.shar (2.28 KB, text/plain)
2015-03-19 13:45 UTC, Nikola Kolev
no flags Details
Updated httpd with alternative name to avoid Apache conflicts (3.21 KB, text/plain)
2015-07-08 20:02 UTC, jsmith
no flags Details
httpd 5.7.20150508 (2.54 KB, text/plain)
2015-11-28 10:14 UTC, Nikola Kolev
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Comment 1 Thomas Zander freebsd_committer 2015-05-17 06:58:15 UTC
Wouldn't it make sense to consider renaming the binary to allow for an installation next to apache?
Comment 2 jsmith 2015-07-08 20:02:29 UTC
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.
Comment 3 Chris Hutchinson 2015-07-21 03:42:46 UTC
(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...
Comment 4 Nikola Kolev 2015-07-21 12:30:38 UTC
/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.
Comment 5 Chris Hutchinson 2015-07-21 14:18:42 UTC
(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
Comment 6 jsmith 2015-07-21 14:56:48 UTC
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.
Comment 7 Chris Hutchinson 2015-07-22 18:19:39 UTC
(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
Comment 8 Nikola Kolev 2015-11-28 10:14:37 UTC
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
Comment 9 commit-hook freebsd_committer 2015-12-06 12:17:56 UTC
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
Comment 10 commit-hook freebsd_committer 2015-12-06 15:42:11 UTC
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