On Thu, Feb 21, 2008 at 07:08:18PM -0500, Alexander Hansen wrote:
> Richard Cobbe wrote:
> It's a Leopard difference. The package was set up to use the system's
> python, but on Leopard that's 2.5 .
> It's likely possible to modify the package just to use "/usr/bin/python
> setup.py build" -- at worst we may need separate Leopard and Tiger
> versions if the package generates stuff that needs a specific python
> interpreter.
I modified the .info file to call /usr/bin/python instead of python2.3 in
two places, and the package built successfully. (To be extremely and
probably unnecessarily precise, I had it call /usr/bin/python2.5 instead,
but the two symlinks eventually point at the same thing on my system.)
In order to get it to run, I had to modify $PYTHONPATH, as
/sw/etc/profile.d/offlineimap.{csh,sh} set it to include
/sw/lib/python2.3/site-packages, but the package actually puts its stuff
into /sw/lib/python2.5/site-packages, as you might expect. With the
obvious change to the environment variable, it ran like a charm.
Thanks to you and Daniel for your help!
(And Daniel, I should have mentioned up-thread that I CC'd offlineimap's
maintainer; he's been getting all these emails.)
Richard
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Fink-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-users