>>> Jack Jansen wrote > Sigh... Don't wait for me to update the Mac-specific files: I've > apparently > messed up the developer tools on my system. It's now a mix between > gcc3.3 > and gcc3, and I keep running into problems. Reverting to gcc3.1 also > doesn't seem to work. My home system has a virgin 10.2 partition, but > I'm > away tonight so I won't have the chance to build and test anything > (and I assume tomorrow-morning-European is too late, right?). I'm 99% > sure that just changing the version numbers in the .plist and .strings > files > won't break anything, but without testing I don't want to chance it. I'm cutting a release candidate tomorrow morning, but the release itself on Friday AU time. If it's just a matter of updating the version numbers in the .plist files, I can do this. Assuming, of course, that just editing the .plist files with vi to s/2.3/2.3.2/ is going to Do The Right Thing. I know of a couple of folks with Macs who could test the framework build - aside from "./configure ; make ; make testall", what else do they need to test? Anthony -- Anthony Baxter <anthony at interlink.com.au> It's never too late to have a happy childhood.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4