SCIFI To MacUpdateAdminGuys&Gals and to these Developers, You–all seem to be missing the point. We Tiger users need a *current* version of these apps, not a moldy *previous* version. ;) I guess I’ll try building from the source tarballs but note it isn’t for the faint–of–heart (that’s what MacPorts users will end–up doing as well). Also note this project in particular looks like it’ll require X11 and all sorts of other non–Mac GUI stuff e.g. GNome, most of which I have already installed locally here as shared libs — thus my build probably won’t be a self–contained one with static libs and I wouldn’t be able to distribute my build for others to use this way — but that’s the way Things Ought To Be™ on a true–blue *ix system for a whole gaggle of technical reasons, most importantly the moldy pre-packaged previous versions will undoubtedly be using old code from the same dependent projects as well. Y’see how Leopard–only developers are ABUSING the open–source traditions here? Do y’all see that??? Yes indeed even Apple have gotten off–track in this regard also — their “promise” of being “more Linux–friendly” is long–long–long gone IMO. This website is going to need a new filter that lists only the apps that are known to be Jaguar–, Panther–, Tiger–compatible vis–à–vis Leopard–only etc. etc. etc. etc. etc. And appropriate options be placed on the Developers “Add A File” panel as Required items before posting the app made publicly available. …ok I had my spiel, bring on the flamewars…
(Version 2.20.3) | 
Main
