From owner-freebsd-ports@FreeBSD.ORG Wed Sep 10 22:00:59 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EABFBA90 for ; Wed, 10 Sep 2014 22:00:59 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 807481EA for ; Wed, 10 Sep 2014 22:00:59 +0000 (UTC) Received: from [192.168.1.239] ([212.98.32.54]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0MPZuP-1XNjL62IaX-004oFr for ; Thu, 11 Sep 2014 00:00:57 +0200 Message-ID: <5410CA7A.6020702@gmx.net> Date: Thu, 11 Sep 2014 00:02:34 +0200 From: Simon Wright User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.1.0 MIME-Version: 1.0 To: freebsd-ports@freebsd.org Subject: [Resolved] Re: Any update planned for www/mod_log_sql2 References: <540ACE6D.3040001@gmx.net> <540B4603.2040004@astart.com> In-Reply-To: <540B4603.2040004@astart.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:bbrAhbA0JhufGiCUcW27HEsgdjoh7C4F7bpw9xwlnzdOfdmtG+S fr2BWyaFmEysjen60TZcjXFrWqpoeXsKRRaH+mQf7HnE8iW3Ja5ajH8c6jaShpdYtwlA5gk 2MY4ZiBjzNhvfOlyH6e1JjTbfArj3F/tqFd0iDOC+gZrKmIdoGqj43HxCQW4YgOSAyHVY6f ZHiNGafKwrxUXQHsla17A== X-UI-Out-Filterresults: notjunk:1; X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Sep 2014 22:01:00 -0000 On 06/09/2014 19:36, Patrick Powell wrote: > On 09/06/14 02:05, Simon Wright wrote: >> >> I was wondering whether mod_log_sql2 will be or can be updated to >> work with the new default of Apache24? Apache22 is specified >> explictly in the Makefile. >> >> I'm not sure whether mod_log_mysql is a replacement/substitute but >> that is also linked explicitly to Apache22. >> >> An indication of any time line or migration path would be much >> appreciated! >> > > I had a quick look at this (Note: I am NOT an Apache module expert, > but I have updated a couple of them that I needed). > > The source code for the module needs to be updated to match Apache > 2.4. There are more than a few trivial changes here. > > I you feel brave, look at: > > http://httpd.apache.org/docs/trunk/developer/new_api_2_4.html > and > http://httpd.apache.org/docs/2.4/developer/modguide.html > and > http://httpd.apache.org/docs/current/mod/mod_example.html Update: Olli Hauer has just committed an update to this port that fixs the outstanding issues :). We have tested it and it works for me with both Apache 22 and Apache 24. I'm not brave but thanks for the links! If I'm feeling brave I *may* go through the code and see how it was fixed . . . but not tonight :). Thanks to Olli for his work to update and tidy-up this port, I'm very grateful! Regards Simon.