OK, the ncurses issue is another complicated one. Both with "fixing" ncurses, and with the gcc 3.3 ABI change, we're going to need to so what we did last time and be careful to do two things: 1) give a new version number to pkgs with C++ code when they are moved to the 10.3 tree 2) make every dependency on other pkgs with C++ code a "versioned" dependency, depending on the NEW version.
The same will apply to ncurses, if this is how we are going to solve that problem. Every package which depends on ncurses will need a new version. Fortunately, I'm in the middle of finding which packages depend on ncurses. Unfortunately, the process is not yet finished. Also, we need to go through and check that all of the packages with C__ code have been properly been tagged with the GCC tag. (By the way, there may be other possible ways of handling all of this, but since Justin started with the 10.3 tree, I'm explaining what we'll need to do if we follow last year's strategy.) For all of the above reasons, I would urge people NOT to put things into the 10.3 tree yet. We're just not ready (although I for one have been working pretty hard to get ready). -- Dave "Justin F. Hallett" <[EMAIL PROTECTED]> wrote: > Update of /cvsroot/fink/fink/10.3 > In directory sc8-pr-cvs1:/tmp/cvs-serv497 > > Modified Files: > ncurses.info ncurses.patch > Log Message: > Updated to need release with fixed ABI, thanks to cirdan > > ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
