From owner-freebsd-ports Wed May 26 7:50: 5 1999 Delivered-To: freebsd-ports@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 457BA14C1B for ; Wed, 26 May 1999 07:50:03 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id HAA97356; Wed, 26 May 1999 07:50:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Wed, 26 May 1999 07:50:02 -0700 (PDT) Message-Id: <199905261450.HAA97356@freefall.freebsd.org> To: freebsd-ports@FreeBSD.org Cc: From: Anton Berezin Subject: Re: ports/11893: new port: www/thttpd Reply-To: Anton Berezin Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR ports/11893; it has been noted by GNATS. From: Anton Berezin To: Anders Nordby Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: ports/11893: new port: www/thttpd Date: 26 May 1999 16:40:10 +0200 Anders Nordby writes: > This is a new port of this tiny/turbo/throttling HTTP server. > Some times Apache just is too much. :-) I think in the current form this port can be quite useless. Thttpd is *quite* configurable, all configuration is done in config.h before the build. For most ports the default configuration is acceptable, but not in this case. Almost everybody will have a need to put his hands into config.h. I would suggest some mechanism for doing this in port (might be as simple as entering an editor at post-configure time; though this will make the port INTERACTIVE, and this is probably a bad thing). -- Anton Berezin The Protein Laboratory, University of Copenhagen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message