Received: by taz.hyperreal.com (8.6.12/8.6.5) id KAA14398; Tue, 30 Jul 1996 10:58:03 -0700 Received: from sierra.zyzzyva.com by taz.hyperreal.com (8.6.12/8.6.5) with ESMTP id KAA14384; Tue, 30 Jul 1996 10:57:59 -0700 Received: from sierra.zyzzyva.com (localhost [127.0.0.1]) by sierra.zyzzyva.com (8.7.5/8.7.3) with ESMTP id MAA04015 for ; Tue, 30 Jul 1996 12:57:57 -0500 (CDT) Message-Id: <199607301757.MAA04015@sierra.zyzzyva.com> To: new-httpd@hyperreal.com Subject: Re: cvs commit: apache/src CHANGES Configuration.tmpl Makefile.tmpl In-reply-to: akosut's message of Tue, 30 Jul 1996 10:39:33 -0700. X-uri: http://www.zyzzyva.com/ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 30 Jul 1996 12:57:56 -0500 From: Randy Terbush Sender: owner-new-httpd@apache.org Precedence: bulk Reply-To: new-httpd@hyperreal.com > If platform X has no (or a broken) regex package, and it can't compile > Spencer's, then what? It seems to me that we *have* to either support the > package, or not use regex capabilities in Apache. And we're already > commited to the latter. Do you know of such a platform? I'm kind of surprised this is that much of a debate... My take on this is that if someone comes along and wants to run on something that A) does not have POSIX regex B) is not supported by Henry's or the GNU package will have as part of their job of porting Apache to bring one of those other two alternatives up to snuff for this most likely very *unpopular* platform. We cannot be responsible for every OS's problems. We provide what we view as being a good alternative to a bad OS implementation of POSIX regex. And we're done.