Hi

It seems that Jay 'Eraserhead' Felice <jfelice@xxxxxxxxxxxx> was the guy doing 
the python port. But seeing that is last check-in was in 2001, I would simply 
ignore the changes. The python code could be branched since it seems it will 
never be updated, we could:
- branch the current HEAD to b0-17-python and not use it anymore.
- update the b0-16 branch with the latest code of the current HEAD without the 
python code.
- promote the b0-16 branch to HEAD.
- go the 1.0 :) I hate 0.x version numbers :)

Three is a limit of keeping 2 branches over 3 years if you want active 
developpement...

Otherwise, we could simply add
#define g_malloc malloc
#define g_free   free
in tn5250-private.h in the b0-16 branch just to have much less discrepancy 
between the branches. For instance, the only differences in macro.c between the 
branches are allocation functions. This doesn't need to be. I'm willing to do 
the g_ adding to the b0-16 branch. As you can see, I have some time to put on 
the project. But I'd prefer my first solution, i.e. create a new "stable" 
release soon and stop keeping unfinished (?) code indefinitely.

By the way, is the python code usable? I can't test this.

Just my 2ÂCAN worth... :)

Marc-Antoine Ruel

PS: By the way, I added a "Choose Font..." menu item and the implementation in 
win32 port. I'm waiting the branch stuff to settle to send you a patch.


> -----Message d'origine-----
> DeÂ: linux5250-bounces@xxxxxxxxxxxx [mailto:linux5250-
> bounces@xxxxxxxxxxxx] De la part de Scott Klement
> EnvoyÃÂ: 24 fÃvrier, 2005 19:07
> ÃÂ: Linux 5250 Development Project
> ObjetÂ: RE: [LINUX5250] win32 update
> 
> 
> Guys,
> 
> Please make sure that when you make changes to anything aside from GLIB
> and Python support, that you make it to BOTH branches (HEAD and b0-16).
> 
> I don't know when (if ever) someone will finish the Python support, so for
> the time being we need to keep making the changes to both branches. If you
> port the code with each individual patch, it's not a lot of work.  If you
> wait until release time and try to mass-port every patch since the last
> release, it's a big headache.
> 
> So please keep the two branches in sync!  Thanks!



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.