On Nov 14, 2007 7:16 AM, Benjamin Bruheim <[EMAIL PROTECTED]> wrote: > More and more software is starting to require python 2.5, but there > are a few issues with upgrading. > > Currently libraries are installed into /Libraries/Python2.4/site-packages - > allowing a system to have libraries for any python version installed > at the same > time. Libraries installed for Python2.4 won't work in 2.5 and have to be > reinstalled. Other distros have their own packages for each python version to > make advantage of this. But other distros are prone to issues if you decide to > change the default python, but I wont go into these. > Upgrades between minor python versions is non-problematic, ie. 2.5 to 2.5.1. > > There are two issues with Gobo and Python when upgrading python: > - Once upgraded to 2.5 you will no longer have any libraries for the new > python-version installed, yet the Dependencies are met for all software. > - Reinstalling a library will remove the previous install for python2.4. > > One solution to the first issue is to add functionality to the python recipe > or > Compile that reinstalls everything that depends on python. Since python > libraries are forward compatible this is not a problem. > > To solve the second issue Compile could check if there are other installed > versions and rename the library name or version to reference the "other" > python > version and that way keep the library. Or warn before removing the old version > of the library. > > Mohjive told me that upgrading the kernel will force a recompile > of all kernel modules. Perhaps using a similar technique would work?
Yes, I believe it's ok to migrate that functionality, which is now tied to the Linux recipe, into Compile. That will certainly help. -- Lucas powered by /dev/dsp _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
