After a discussion on IRC last night, I have a completely different proposal to make about the gcc 3.3 upgrade.
In the new proposal we make a new distribution, perhaps called 10.2a, which is for packages running under 10.2 but compiled with gcc 3.3. Peter O'Gorman and others believe that version 3.3 will be the last time that ongoing gcc development foists this kind of binary incompatibility on us; if that is the case, then my more complicated system with /sw/lib3.3 should probably be avoided in favor of doing this upgrade once and for all. While we are at it, we can implement MACOSX_DEPLOYMENT_TARGET and fink prebinding in the 10.2a distribution. We may also be able to fix some other things, like errors in some Shlibs fields. I know that Chris Z. would like to put a binary-incompatible ncurses into the new tree in order to fix a versioning problem with ncurses. Before doing this, though, we need to have some idea of how users are going to upgrade. One simple way is to just increase all revision numbers by 10 as things go into the new tree, like we did for the 10.1->10.2 conversion. However, there were a number of headaches during that upgrade, so it's definitely worth thinking about for a while in advance, to see if we can avoid as many headaches as possible. With this strategy, we'll still need a separate 10.3 distribution, but we can expect many fewer changes will be needed to construct it -- one of the major differences will be that we compile with MACOSX_DEPLOYMENT_TARGET=10.3 in that case. -- Dave ------------------------------------------------------- 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/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
