Re: Proposal for making the GtkFileChooser code asynchronous

Murray Cumming wrote:
We might consider GNOME to be 3rd-party code. If someone installs this
future GTK+ 2.10 without also updating the rest of GNOME then GNOME would
be broken. Smart package-managers would prevent this situation, of course.
Maybe we can live with that.

You mean distributions that have active packaging will prevent that situation. But not everybody uses package managers to install GNOME, or use a distribution which has the latest GNOME. Suppose someone uses Fedora 3 or something. Newer GNOME RPMs for Fedora 3 will not appear. He sees an application he wants to use, and installs the app from source. The app requires GTK 2.10, so he downloads GTK 2.10 from source, compiles and installs it, and BAM - he broke his entire desktop environment. Or what if somebody uses Linux From Scratch and builds everything from source? If he wants to use that app which depends on GTK 2.10, not only must he install GTK 2.10, but also recompile the entire GNOME stack.

Compatibility should not be taken lightly. It doesn't mean that innovation is impossible, it just means you have to be more careful.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]