On Tue, Jun 01, 2004 at 01:18:57AM -0700, Denis Leroy wrote:
> Should we commit the gcdmaster code to gtkmm 2.4 (and sigc++ 2.0) ? I
> was looking over the gtkmm 2.4 patch that was submitted recently, and
> it's working fine. Unfortunately, gtkmm 2.4 is not backward compatible
> (mainly, but not only, because of the sigc++ 2.0 "upgrade"). It's
> possible to keep both compatible through autoconf magic, but it'd
> require adding #ifdef's all over the code and is definitely not a
> viable long-term solution. What do'y all think ?
I see 2 paths:
*) Tag the current release as gcdmaster_last_2_2 and commit the 2.4 patch.
Development will continue on the 2.4 version only.
*) Create a gcdmaster_2_4 branch
Either way I'd suggest to build a source distribution of the last 2.2 code
and make it available, and to place a note on the homepage/Changes stating
that development is going on in the 2.4 branch.
--
Giuseppe "Cowo" Corbelli ~\/~ My software: http://cowo.yoda2000.net
-<! WINDOWS: l'unico sistema che puo' inchiodarsi tra un crash e l'altro !>-
|
