On Tue, 2010-03-30 at 04:10 +0200, Vincent Untz wrote:
> Can we get a 2.30.0.1 tarball that uses some non-deprecated API or, even
> better, that doesn't use -DGTK_DISABLE_DEPRECATED by default?
Ugh, sorry about the breakage. I'm building Evo on GTK+ for GNOME 2.28;
that's why I didn't notice thi
On Tue, 2010-03-30 at 10:18 -0400, Matthew Barnes wrote:
> On Tue, 2010-03-30 at 15:35 +0200, Vincent Untz wrote:
> > Le mardi 30 mars 2010, à 09:18 -0400, Matthew Barnes a écrit :
> > > Even better, can we get a macro added to gnome-common that implements
> > > this deprecation flag policy, and pe
On Tue, 2010-03-30 at 15:35 +0200, Vincent Untz wrote:
> Le mardi 30 mars 2010, à 09:18 -0400, Matthew Barnes a écrit :
> > Even better, can we get a macro added to gnome-common that implements
> > this deprecation flag policy, and perhaps even set a GNOME Goal for it?
>
> Sure, it'd be nice to hav
Le mardi 30 mars 2010, à 09:18 -0400, Matthew Barnes a écrit :
> On Tue, 2010-03-30 at 04:10 +0200, Vincent Untz wrote:
> > Can we get a 2.30.0.1 tarball that uses some non-deprecated API or, even
> > better, that doesn't use -DGTK_DISABLE_DEPRECATED by default?
>
> Even better, can we get a macro
On Tue, 2010-03-30 at 04:10 +0200, Vincent Untz wrote:
> Can we get a 2.30.0.1 tarball that uses some non-deprecated API or, even
> better, that doesn't use -DGTK_DISABLE_DEPRECATED by default?
Even better, can we get a macro added to gnome-common that implements
this deprecation flag policy, and
Le jeudi 25 mars 2010, à 15:45 -0600, Federico Mena Quintero a écrit :
> On Wed, 2010-03-24 at 09:55 +0100, Frederic Crozat wrote:
> > Le 23/03/2010 19:22, Federico Mena Quintero a écrit :
> > > On Tue, 2010-03-23 at 13:52 +0100, Vincent Untz wrote:
> > >
> > >> I'm a bit worried that people using