I've got most everything building (including another attempt at a kdemultimedia package). There are still some minor issues but 3.2 is looking pretty sweet.
I'm hoping to release Fink packages to unstable in the next week or two if things go as planned, my last remaining issues are:
-
Find out why a number of the MS Office import plugins in KOffice still aren't working. It's not obvious...
-
Find out why the arts esound driver broke, it's just spitting out noise now.
-
Run all the KDE apps long enough to see if they have any obvious issues.
-
See if there's a workaround for the '*' bug in konsole (and possibly elsewhere). Every time I think we've got a lead it only works some of the time. 😛
-
See if there's any way to fix KDE completely freaking out when using apple-wm on panther.
wow, i am impressed and amazed. this sounds great indeed. i just hope you make available the patches and instructions (if needed) for those of us who prefer not to use fink. if not, oh well, be able to figure it out from looking at the cvs source tree, but stilll. it’d be nice.
Assuming the patches aren’t fink-specific, I’ll check them in to KDE CVS (KDE 3.2 CVS just about builds out of the box now; I’ve been committing fixes as I’ve found them).
How are things going on the building-KDE-without-X11 front?
There’s still a lot of Fink work to catch up on before I can take much time to look at it again. Feel free to port it in the meantime… 😉
Mac Hardware and Linux Software
Ranger Rick is almost ready to release KDE 3.2 to Fink unstable. And he’s working with an OS X developer on fixing the cpp on Panther issue, which is preventing me from successfully starting X on my iBook. Can’t wait till he’s done. Once I get Fink run…
Mac Hardware and Linux Software
Ranger Rick is almost ready to release KDE 3.2 to Fink unstable. And he’s working with an OS X developer on fixing the cpp on Panther issue, which is preventing me from successfully starting X on my iBook. Can’t wait till he’s done. Once I get Fink run…
About the Office filters problem. Any chance it could be an endian issue? I seem to remember that MS just writes raw data structs to disk with office files (which explains why different versions of Office even have problems reading them). If so, changing the endian-ess on them could screw things royally.