libxml2 python subport

Joe Marcus Clarke marcus at marcuscom.com
Thu Jan 15 11:33:02 PST 2004


On Wed, 2004-01-14 at 22:40, Khairil Yusof wrote:
> On Wed, 2004-01-14 at 12:43 -0500, Joe Marcus Clarke wrote:
> 
> > Is this really necessary?  libxml2 builds with Python supported enabled
> > by default.  No one has complained thus far.
> 
> I ran into a problem, in porting a zope component that's dependent on
> libxml2.
> 
> I'll try to make the situation clearer.
> 
> zope ports uses python2.1 (lang/python21)
> third-party python modules/ports are installed by default for latest
> version (in this case 2.3)
> 
> So any zope port, will not find required dependencies (or work if you
> hack it) because it will look in python2.1 directory, not python2.3.
> 
> I'm trying to figure out the best way to have multiple python versions
> of libxml2 python bindings based on existing ports.
> 
> - sub port (which is how the rpm is done) and will always automatically
>   follow latest libxml2 port.
> 
> or
> 
> - independent port using python binding tarballs released by xmlsoft.
>   but you always have to chase libxml2 port everything new version
>   is released.
> 
> or
> 
> - tell users you can only have one libxml2 python binding for one
>   python version at runtime build only, using with PYTHON_VERSION=X
> 
> Please advise, on what you think is best.

Go ahead and create a slave port to libxml2 that installs the Python
bindings needed for zope.  Once that's done, I'll update libxml2 to
support slaves.

Joe

-- 
PGP Key : http://www.marcuscom.com/pgp.asc


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-python/attachments/20040115/e7f8ea00/attachment.bin


More information about the freebsd-python mailing list