Date: Sun, 18 Sep 2005 10:44:06 -0500 From: linimon@lonesome.com (Mark Linimon) To: Gavin Atkinson <gavin.atkinson@ury.york.ac.uk> Cc: kris@freebsd.org, python@freebsd.org Subject: Re: Fixing port www/zope-cmfphoto Message-ID: <20050918154406.GA5846@soaustin.net> In-Reply-To: <20050918101327.H86911@ury.york.ac.uk> References: <20050918101327.H86911@ury.york.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Sep 18, 2005 at 11:04:27AM +0100, Gavin Atkinson wrote: > my first attempt at understanding the ports build infrastructure. Well, you've chosen a complex topic on which to dive into it :-) > Despite zope-cmfphoto declaring it requires Python 2.3 (indirectly, via > the USE_ZOPE=yes option), somehow RUN_DEPENDS is being populated with > py24-imaging-1.1.5.tbz rather than py23-imaging-1.1.5.tbz - presumably > this is being done by the pointyhat build scripts based soley on the fact > that it is the newest/default version? As best I can tell the pointyhat scripts use packages as prerequisites for every port that gets built. (Otherwise, the amount of time required for the builds would be vastly increased). My guess is that the default package of py-imaging maps to py24-imaging rather than py23-imaging. Let's see if that's correct .... Here is a graphical map of the dependencies as seen by a system that has Python 2.4 installed on it: http://portsmon.FreeBSD.org/portdependencytree.py?category=www&portname=zope-cmfphoto So www/zope-cmfphoto depends on lang/python23 and graphics/py-imaging; but graphics/py-imaging depends on lang/python (2.4), which would, when compiled in a clean system, indeed produce package py24-imaging, not py23-imaging. So this may be more a problem with the framework, not with pointyhat (e.g. the fact that you can only depend on a port, not a specific package of it). My guess would be that we need to mark these as NO_PACKAGE as a workaround until Zope can fix their code to not rely on 2.3, as some of these other ports have done. > Are the pointyhat build scripts available publically for me to try and > figure out further what the issue is? The port builds and installs fine > from source, and a package generated from that seems to be correct too. See http://www.freebsd.org/cgi/cvsweb.cgi/ports/Tools/portbuild/scripts/buildscript , but be warned that the scripts are very dense and will not quickly provide you any answers. mcl
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050918154406.GA5846>