I'm working on packages to use with zope, and have got first cuts on the egenix-mx-base utilities and psycopg, postgresql for Zope.
I ran into the same type of versioning problem building psycopg that was mentioned in conjunction with autoconf, the configuration and Makefiles all wanted to find %{l_prefix}/lib/python2.3. I worked around it with judicious use of "shtool subst -s" and "make VERSION=''", but this is something of a PITA.
While I understand the philosophy of building without the release in names, there are many packages that have the versioning built deep into their autoconf, automake, and libtool files (in particular in the aclocal.m4 files often specify full versioning and some of the automake stuff gets pretty strange -- can you spell amd :-). BTW: I'm building with all the autotools from OpenPKG, so it's not getting anything from the base system.
It might be better to have symbolic links in the packages that would allow the clean, version free style, as well as versions.
I'm curious about how the packages which break are building: do they use distutils from within the makefile (e.g., '$PYTHON setup.py build')?
I recall that the mx stuff was not distutil-ified the last time I looked at it, anyway.
Tres. -- =============================================================== Tres Seaver [EMAIL PROTECTED] Zope Corporation "Zope Dealers" http://www.zope.com ______________________________________________________________________ The OpenPKG Project www.openpkg.org Developer Communication List [EMAIL PROTECTED]
