Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 22 Jul 2015 18:19:39 +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-k0WwOeaFW4@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 #7 from Chris Hutchinson <portmaster@bsdforge.com> ---
(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

-- 
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-k0WwOeaFW4>