[SM-Discuss] GTK+2 UPDATE REVERTED

"Andraž 'ruskie' Levstik" ruskie at codemages.net
Wed Sep 10 15:15:23 EDT 2008


On 21:05:28 2008-09-10 Eric Sandall <eric at sandall.us> wrote:
> On Wed, 10 Sep 2008 13:35:28 -0500
> George Sherwood <pilot at beernabeer.com> wrote:
> > Nothing requiring gtk 2.14.x that I know of, but I am absolutely
> > against keeping this revert in the test grimoire.  First it is
> > against a process that has been in use the many years that I have
> > been a developer and lead developer.  Essentially we are leetting Vlad
> > circumvent the process as he has done in the past.  Secondly we will
> > not get enough testing to understand how widespread it is among our
> > developers/users.  As far as creating a GNOME devel branch, IMO this
> > will not provide the necessary amount of testing that we need for gtk
> > which crosses many more boundaries than GNOME.  
> >  
> > I understand that this flicking when starting applications might be
> > annoying to Vlad, but doesn't result in a broken system and there are
> > workarounds to include him reverting the changes on his machine.
> >  
> > I would request that we put gtk 2.14.x back into the test grimoire in
> > order to more fully understand the issue vice sitting back on our
> > heels.
> >  
> > George Sherwood
> 
> IMO, test is for testing our packages, not specifically for testing
> upstream bugs. ;) Flickering might be annoying, but depending on how
> much flickering it could make it unusable (eye strain, headache, etc.).
> Do we know of any patches that may mitigate the issue?
> 
> I have no issue with updating gtk+2 again, but what do others think?
> George is for it, Vlad against it, and I am fine either way (I have
> yet to try the possibly broken gtk+2), so I am not helping much. ;)
> 

Same here... haven't really updated yet and probably won't for a while.

--
Andraž "ruskie" Levstik
Source Mage GNU/Linux Games grimoire guru
Geek/Hacker/Tinker

Be sure brain is in gear before engaging mouth.
Quis custodiet ipsos custodies.
Ryle hira.

Key id = F4C1F89C
Key fingerprint = 6FF2 8F20 4C9D DB36 B5B6  F134 884D 72CC F4C1 F89C



More information about the SM-Discuss mailing list