Jeremy Henty wrote these words on 05/13/06 07:49 CST: > Yes. The GTK+ team are outstandingly good at preserving backward > compatibility. I have done many upgrades of GTK+-2.4.x,2.6.x,2.8.x > (and also glib, atk, pango) without problems. I've never had to > uninstall the old version and never had to recompile anything.
Not to argue, but instead point out a different experience, just recently (in the last couple of weeks), I updated a perfectly working system (a test system that I knew I really didn't need any longer) from GTK+ 2.8.9 to 2.8.17 and it totally hosed Evolution. Evolution simply hung every time it tried to download (know that the GTK+ update included updates to ATK, Pango, Glib, Cairo, et all) Additionally, I have had issues going from one major release (2.6) to another (2.8) on many occasions. For example, the ...mm binding packages need to be matched, so there are definitely compatibility issues. I remember also a time when the BLFS book was updated to a Glib/GTK combination that had to be backed out because it hosed the existing GNOME version in the book. So, there has been many times where folks have encountered a different experience than what Jeremy is reporting. -- Randy rmlscsi: [bogomips 1003.27] [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] 07:55:01 up 23:55, 3 users, load average: 0.34, 0.22, 0.08 -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
