Return-Path: Delivered-To: apmail-httpd-apreq-dev-archive@httpd.apache.org Received: (qmail 43030 invoked by uid 500); 23 Jan 2002 12:23:55 -0000 Mailing-List: contact apreq-dev-help@httpd.apache.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Post: List-Help: List-Unsubscribe: List-Subscribe: Delivered-To: mailing list apreq-dev@httpd.apache.org Received: (qmail 43017 invoked from network); 23 Jan 2002 12:23:55 -0000 To: Issac Goldstand Subject: Re: 1.0 in CVS? Cc: apreq-dev@httpd.apache.org References: <3C4EA7A6.8090803@beamartyr.net> From: Joe Schaefer Date: 23 Jan 2002 07:25:05 -0500 In-Reply-To: Issac Goldstand's message of "Wed, 23 Jan 2002 14:08:06 +0200" Message-ID: Lines: 29 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.5 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Issac Goldstand writes: > Joe Schaefer wrote: > > >A few days ago I added a patch for 5.005thread support. > >Are there any problems with the current CVS that would > >prevent us from releasing it? > > > I haven't had any problems (yet), but I haven't aggressively tested > everything yet, either... Is the documentation complete and up-to-date? > I know I've run into that before a lot. > > Issac The most recent patches were doc patches, mainly for Request.pm and Cookie.pm (and the ToDo). The INSTALL document is probably wrong wrt autoconf support- we don't currently include a working ./configure script. I put some text in README to help C programmers roll their own libapreq.a, but it's hardly an optimal solution. To facilitate testing, I tarballed the current CVS. You should be able to grab it from http://www.apache.org/~joes/libapreq-1.0-rc1.tar.gz Feedback, even if it's positive, is always appreciated :-) -- Joe Schaefer