From owner-freebsd-apache@FreeBSD.ORG Fri Nov 8 20:15:19 2013 Return-Path: Delivered-To: apache@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 ESMTP id 806DA9A3 for ; Fri, 8 Nov 2013 20:15:19 +0000 (UTC) (envelope-from ohauer@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 16CFB2E86 for ; Fri, 8 Nov 2013 20:15:18 +0000 (UTC) Received: from [192.168.0.100] ([87.139.233.65]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0MDn8s-1VOyxc1XFW-00H6lX for ; Fri, 08 Nov 2013 21:15:10 +0100 Message-ID: <527D464D.20501@gmx.de> Date: Fri, 08 Nov 2013 21:15:09 +0100 From: olli hauer User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: apache@freebsd.org Subject: Re: FreeBSD Port: www/mod_python3 References: In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:ejaB7DBXdCvXEvUqp3lwxQc2XFoKW534K4otf/Ti/i7gcw9xu/Z HiadFctpJuBnEx/oyr8ef5kCPeZKdQK8GeOGkReQJINwtgOCvnfmXTCTvfmxkvsblb96WHI Sos1+VmhI2wJzNpRNzv/9mG4n1vOrGghGZ73jlRJuTAxxaDnee+xP8R2PzZJWpSZUyHCCVK fb81uxI5MrYV/6rLmyenA== Cc: Sam X-BeenThere: freebsd-apache@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Support of apache-related ports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Nov 2013 20:15:19 -0000 On 2013-11-08 18:11, Sam wrote: > Hi! Just wondering if it would be possible to update mod_python in the > FreeBSD ports to 3.4.1 which is the latest version as of October 23rd, > 1013. It can be found here: http://dist.modpython.org/dist/ > > You are listed as the maintainer of this port but if I should be > asking someone else or going about this in a different way please let > me know. > Normally the maintainers are getting a New Version mail but here the distribution place has changed from apache to the project site so the new version was not detected ... I've done a quick test and it seems at first the official distfile is not really usable to build packages. For example in the official source they try to resolve the version via git, this will work maybe on the dev system but not in clean build environments +version.c: + @MP_GIT_SHA=$$(git describe --always); \ + echo > version.c ; \ + echo "/* THIS FILE IS AUTO-GENERATED BY Makefile */" >> version.c ; \ + echo "#include \"mp_version.h\"" >> version.c ; \ + echo "const char * const mp_git_sha = \"$${MP_GIT_SHA}\";" >> version.c ; \ Arrrg, even no Changelog entry +.. _changes: + +******* +Changes +******* + ... old version changes ... Perhaps the version 3.4.1 could become a testing port but with such issues I see after the first look no reason to replace 3.3.1 with 3.4.1. -- olli