Update to the latest revision of of pymol in unstable first before you do a 'fink update-all', it uses python22 now not python although it will want to install python-2.2.2 as it has a build depends on this to ensure that numeric and pmw get installed in the right spot, and afterwards you can then upgrade to python-2.3 and pymol will still work happliy, although if you rebuild/upgrade numeric or pmw once python-2.3 is installed you will break pymol. :( Or don't run unstable.
Cheers Matt
On Monday, Mar 3, 2003, at 04:00 Australia/Sydney, Koen van der Drift wrote:
Hi all,
I recently did a selfupdate-cvs, and noticed that a new version of python
is available. It's an alpha release, so I guess it will be followed by yet
anoother alpha, a couple of beta releases and then the final release. I'm
on a dialup connection, and I rather not d/l all those MB's each time
python gets upgraded. I don't use python directly, but a package that
depends on it (pymol).
So would it be possible to have a choice to either install the current
python (2.2.2) or the new one (2.3)? Hopefully this then also prevents a
update whenever I do a update-all.
thanks,
- Koen.
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Fink-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-users
