Hi All,
I wondered what people's thoughts are on our support for GTK+ 2.20... A quick check reveals that we now have 100 conditional code blocks to support the obsolete symbols provided by GTK+ 2.20, so it adds a bit of a burden on developers and it makes the code horrible to read in places. Most stable/LTS releases of major linux distros provide newer versions of GTK+/gtkmm than 2.20. The exception is Debian Stable, but that's a pretty special case (i.e., ancient versions of everything!)
If we were to drop our support for gtk+ 2.20, the main casualty would be Ubuntu Lucid. However, (a) there are two newer stable versions of Ubuntu and a newer LTS release available, (b) we have already bumped our Cairo dependency to a version that is not in Lucid, and (c) I guess that trunk will inevitably reach the point where we leave some older distro versions behind.
So... the question is whether we continue supporting a big chunk of conditional code or whether we drop support for gtk+ 2.20.
Any thoughts?
AV
El 30/06/12 09:43, Alex Valavanis escribió:
Hi All,
I wondered what people's thoughts are on our support for GTK+ 2.20... A quick check reveals that we now have 100 conditional code blocks to support the obsolete symbols provided by GTK+ 2.20, so it adds a bit of a burden on developers and it makes the code horrible to read in places. Most stable/LTS releases of major linux distros provide newer versions of GTK+/gtkmm than 2.20. The exception is Debian Stable, but that's a pretty special case (i.e., ancient versions of everything!)
If we were to drop our support for gtk+ 2.20, the main casualty would be Ubuntu Lucid. However, (a) there are two newer stable versions of Ubuntu and a newer LTS release available, (b) we have already bumped our Cairo dependency to a version that is not in Lucid, and (c) I guess that trunk will inevitably reach the point where we leave some older distro versions behind.
So... the question is whether we continue supporting a big chunk of conditional code or whether we drop support for gtk+ 2.20.
Any thoughts?
AV
Hi. Debian Testing is currently in freeze stage and the release of Debian 7 is planned for early 2013. Ubuntu Lucid hits end of life for final users in 2013 too. I doubt that a Debian stable user that would keep Debian 6 after version 7 is released is somebody who would need the latest version of inkscape, and Ubuntu Lucid users will have to upgrade anyway because they'll go unsupported for everything (not just inkscape) so your proposal doesn't sound like a big compromise. I'd say +1 :-)
Gez
2012/6/30 Guillermo Espertino (Gez) <gespertino@...400...>:
Hi. Debian Testing is currently in freeze stage and the release of Debian 7 is planned for early 2013. Ubuntu Lucid hits end of life for final users in 2013 too. I doubt that a Debian stable user that would keep Debian 6 after version 7 is released is somebody who would need the latest version of inkscape, and Ubuntu Lucid users will have to upgrade anyway because they'll go unsupported for everything (not just inkscape) so your proposal doesn't sound like a big compromise. I'd say +1 :-)
+1 for me as well.
I was always of the opinion that stable releases have their own, stable versions of Inkscape. The benefits of providing a new program that can run with very old libraries far outweigh the burden of dealing with these old libraries.
Regards, Krzysztof
Hi All,
If there are no opposing voices, I'll go ahead and remove GTK+ 2.20 support within the next couple of days.
I have opened a report [1] to track this. Please let me know if there are any objections.
Thanks,
AV
[1] https://bugs.launchpad.net/inkscape/+bug/1020494
On 1 July 2012 15:19, Krzysztof Kosiński <tweenk.pl@...400...> wrote:
2012/6/30 Guillermo Espertino (Gez) <gespertino@...400...>:
Hi. Debian Testing is currently in freeze stage and the release of Debian 7 is planned for early 2013. Ubuntu Lucid hits end of life for final users in 2013 too. I doubt that a Debian stable user that would keep Debian 6 after version 7 is released is somebody who would need the latest version of inkscape, and Ubuntu Lucid users will have to upgrade anyway because they'll go unsupported for everything (not just inkscape) so your proposal doesn't sound like a big compromise. I'd say +1 :-)
+1 for me as well.
I was always of the opinion that stable releases have their own, stable versions of Inkscape. The benefits of providing a new program that can run with very old libraries far outweigh the burden of dealing with these old libraries.
Regards, Krzysztof
Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
participants (3)
-
Alex Valavanis
-
Guillermo Espertino (Gez)
-
Krzysztof Kosiński