On 11.06.2018 16:03, Eric Williams wrote: > This is incorrect, the deprecation scheme in GTK (at least GTK3) was quite > aggressive but not quite as bad as you've listed it here. > > GTK2.24 was released in 2011. That is the final and stable version of GTK2. > This > is (roughly) when GTK3 development began. GTK3 deprecated a lot of the API > from > GTK2, and while they are deprecated they will not be removed until GTK4. This > means GTK2 API support should (in theory) work until GTK4 released, which is > now > roughly 7-8 years. During this 7-8 years of GTK3 development, you have the > option to use the interim releases of GTK3, or continue to use GTK2. The same > will be true when GTK4 is released -- API deprecated by GTK4 won't be removed > until GTK5, and so on.
That just buys you another 2 years (mind you, the last plan I've read is to have a new GTK+ version every two years, if that has changed, I'm not aware of it) and still requires a relinking against the new library version, if I got that right. So you get 2 years of instability, 2 years of stability, and 2 years of "it should be working" when compiling it against the latest unstable/in-development version. That still doesn't sound great to me. But ultimately seems like that discussion is off-topic in here. _______________________________________________ platform-dev mailing list platform-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/platform-dev
