Ken Moffat wrote these words on 11/04/10 14:41 CST: > I had forgotten, while testing Python-2.7 (and eventually deciding > to stay with 2.6 for the moment), that there is a newer 2.6 release. > With most after-LFS packages I can work out what to rebuild if I > have to upgrade, but for python I don't have a clue. > > If I upgrade within the same series, can I just rebuild python, or > do I need to rebuild everything that has created files in > site-packages/ (cairo, gamin, (lib)gsf, gtk2, libxml2, libxslt, > pygtk, xcbgen (from xcbproto), xml2po (from gnome-doc-utils) ?
Good question. I wish I had a firm answer. I've never updated Python directly into an existing installation because of the issue you mention in your second paragraph. I have renamed an existing /usr/lib/python2.6 directory to something else (.SAVE or whathaveyou) and then installed a new Python in order to update the book, knowing that the existing BLFS installation was near the end of its lifespan. I would hazard a guess that it would be safe to upgrade in place. The existing modules you mention should be okay because there should be no API/ABI changes from 2.6.4 to 2.6.6 in the Python series. But as I mentioned, that is just a guess. -- Randy rmlscsi: [bogomips 1003.28] [GNU ld version 2.16.1] [gcc (GCC) 4.0.3] [GNU C Library stable release version 2.3.6] [Linux 2.6.14.3 i686] 14:46:00 up 2 days, 20:40, 1 user, load average: 0.04, 0.05, 0.00 -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
