Wireshark-dev: Re: [Wireshark-dev] [Wireshark-commits] rev 24770: /trunk/packaging/ /trunk/packaging/nsis/: Makefile.nmake wireshark.nsi /trunk/packaging/portableapps/win32/: makenmake.pl /trunk/packaging/u3/win32/: makenmake.pl

From: Andrew Hood <ajhood@xxxxxxxxx>
Date: Sat, 05 Apr 2008 11:25:58 +1100

Gerald Combs wrote:
> [ I'm replying to -dev instead of Stephen directly since this warrants a more
> detailed and public explanation. ]
> 
> We have indeed decided to drop GTK1 support*. The main reasons are:
> 
>   - GTK1 has been unsupported by the GTK+ team for a long time now. The fact
>     that we've been able to use it up to this point (that is, GTK1 + GLib2)
>     has been due to random chance. That went away with recent GLib2 releases.
> 
>   - Having to support GTK1 has been holding us back in a lot of areas, and
>     has added a lot of maintenance overhead. Dropping GTK1 means we can
>     modernize the column configuration, coloring rules dialog, and lots of
>     other things.
> 
>   - Now that 1.0 is out, if someone needs GTK1 (e.g. Windows users forced to use
>     8-bit color), they have a supported version to fall back on.
> 
>   - The GTK team is working on GTK+3. Our #ifdef situation is bad enough with
>     two versions of GTK. Three will just add to the pain.
> 
> 8-bit color seems to be the only sticking point, in that it is possible that we
> could come out with Wireshark 1.2 or 2.0 before the issue is fixed in GTK2. I
> think this is vastly outweighed by the advantages of dropping GTK1.
> 

Does this mean that those of us who have no choice but to run GTK1
versions because Remote Desktop can only be relied on to supply 8 bit
colour will stop getting security related fixes?

Or will the GTK people finally get off their backsides and fix it?

-- 
There's no point in being grown up if you can't be childish sometimes.
                -- Dr. Who