I suspect it is not as difficult as that. Ask Horst - Horst are you there to comment as I'm sure he is on Debian and using 2.6. I've compiled 2.6 from source a number of times myself. If 2.4 gets broken in the process I don't think it matters as by the time gnuMed is clinically useable 2.4 won't be available!
Yes we can do it file by file, however there are real advantages to gui-design by using 2.6 - lots of the 2.4 gui-bugs have disappeared. Regards Richard On Mon, 5 Sep 2005 04:45 pm, Sebastian Hilbert wrote: > On Monday 05 September 2005 05:09, Richard Terry wrote: > > Yes I'm a pest. > > > > As most distributings are coming supplied with wxPython2.6 now, I really > > think we should debate biting the bullet and upgrading the code to make > > it 2.6 compatible. I'm more than prepared to help with this. > > > > Can we debate this again? It would certainly make migrating to an > > improved gui easier. > > > > Richard > > Here are the facts. > SUSE wxpython 2.5.3, no updated available, 2.6.1 does not easily compile > Debian Sarge, Sid wxpython 2.4 , > > My opinion. Code is mostly fit for 2.6. We cannot move to 2.6 entirely if > it breaks 2.4. > > Lets discuss this file by file. If you find something, suggest a change and > we will test it. > > Sebastian _______________________________________________ Gnumed-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnumed-devel
