By RangerRick, on December 17th, 2005%
Finally got MonoDevelop working again. Looks like the last hurdle was mozilla — for some reason, gecko-sharp (or mono 1.1.10/1.1.11, or something) was bombing with the mozilla 1.7.5 libraries. I’ve changed the dependencies to use firefox instead, and everything works. (Yay!)
Amarok: updated to 1.3.7, changed to allow the choice of backends: xine, gstreamer, or both
amrnb: new package, a speech codec used for mobile phones
Cocoa#: resurrected package, a Cocoa interface for Mono
Gecko#: updated to use firefox libraries instead of mozilla
GStreamer: new packages for GStreamer 0.10 (gstreamer, gst-plugins-base, gst-plugins-good, gst-plugins-ugly)
IKVM: updated to 0.22.0.0
libgdiplus: updated to 1.1.11
liboil-0.3: new package, a CPU optimization library
libsmoke: resurrected package, library for making Qt language bindings
Mono: updated to 1.1.11
MonoDevelop: updated to 0.9 — and it even works 😉
Mono Tools: updated to 1.1.11
MonoDoc: updated to 1.1.11
perl modules: updated a number of perl modules, cleaning up installation, as well as some version bumps:
DBI: updated to 1.49
Digest: updated to 1.14
IO::Stringy: updated to 2.110
MailTools: updated to 1.67
Mime-Tools: updated to 5.418
Net::Jabber: new package, version 2.0
Net::XMPP: new package, version . . . → Read More: Mono updated to 1.1.11 — MonoDevelop is working!!
Share on Facebook
By RangerRick, on September 15th, 2005%
Been making some good progress on getting KDE 3.4 to stable. If you’re interested in seeing what all needs to be moved, you can check the KDE Packaging Progress page on the Fink Wiki. As for packaging, I’ve got qt3 updated to 3.3.5. It turns out it has the annoying attribute of actually honoring the <includehint> entries in .ui files and is causing some of KDE to break. I’m working my way through all of the KDE packages to fix the bad .ui files now and should have them all cleaned up soon. In the meantime, if you’re building KDE and have failures, revert to qt 3.3.4 and try again.
Share on Facebook
Share on Facebook
By RangerRick, on October 21st, 2004%
I’ve finally got KDE 3.3.1 released. There’s still work to do (updating some apps, getting kdevelop updated, etc.) but it should be good for a first run. Phear!
Share on Facebook
Share on Facebook
By RangerRick, on June 23rd, 2004%
I’ve put KDE 3.2.3 in Fink unstable (both 10.2-gcc3.3 and 10.3). It’s looking pretty solid, I’m gonna wait for some input and then I think it’s the first 3.2.x release that will be worth releasing to stable. Now it’s time to start packaging qt 3.3 and KDE 3.3 alpha.
Share on Facebook
Share on Facebook
By RangerRick, on May 3rd, 2004%
I’ve got a new CheeseTracker binary built for Mac OS X, using Qt/Mac 3.3. It’s looking pretty good, although sometimes it freezes on logout, seems to be some kind of thread-locking issues in CoreAudio. If you want to give it a try, you can grab it here. I’ve registered with VersionTracker so I can put it up there as well. Whoo!
Share on Facebook
Share on Facebook
By RangerRick, on March 7th, 2004%
It’s a nice lazy Sunday afternoon. My roommate and I got a grill, we’re cookin’ up burgers, and it’s a nice 66 degrees outside. I’ve got an XFree86 4.4 package working, it seems to run really nice. It’s pending inclusion in unstable after we decide how we want to handle the licensing issue. The main question now is, do we stand with the other distros in not releasing 4.4 packages so that XFree86 is more likely to unkink their licensing, or do we release anyways (since it seems like, at least, there isn’t a conflict anymore)? Also, I’ve basically got KDE 3.2.1 done now. I’m finishing up the test builds on 10.3, but I see no reason it won’t be releasable to coincide with the tarball release from the KDE folks. I’ve got my KDE/Mac toolset put back together and I’m through kdelibs in building everything again (including an update to Qt 3.3.1, I’ve gotta get packages put together and up on the KDE binary page). Things are moving along in a generally forward direction, as mom would say. I’ll keep you posted when I get new KDE/Mac binaries together and ready for perusal.
Share on Facebook
Share on Facebook
By RangerRick, on February 7th, 2004%
KDE 3.2.0 for Fink Released
KDE 3.2.0 is now available in the unstable 10.3 (Panther) tree. This release contains significant new features and bugfixes.
For a general idea of what’s changed, see the official announcement at:
http://www.kde.org/announcements/announce-3.2.php
The following is a list of changes related specifically to the Fink release of KDE:
qt 3.2.3 has had a number of bugfixes, including fixes to using Qt with qmake-based projects, and a few minor speed boosts most of the changes from the KDE 3.1.x series in Fink have been sent upstream to the KDE folks so the amount of patches in the current fink packages are considerably smaller KOffice is back, although not all filters work yet. Expect revisions as things get cleaned up. Some post-3.2.0 patches are in these packages as well, to fix several big bugs that were found after the initial release by the KDE team.
Availability
KDE 3.2.0 is available in both the 10.2-gcc3.3 and 10.3 trees, in unstable.
Installation
To install these packages you will . . . → Read More: (Announcement Sent to fink-announce) KDE 3.2.0 and KOffice 1.3 in Fink Unstable
Share on Facebook
By RangerRick, on January 22nd, 2004%
So it turns out a lot of the launch problems we were having were not, in fact, caused by fork (although the fork can still cause issues). To set up KDEDIRS and PATH and such, we had been making the app bundle contain a shell script that calls the binaries, but behind the scenes, the shell script was still calling, say, /opt/kde/bin/kcmshell. Qt, however, can only figure out where it’s at if it’s called from inside an app bundle.
The fix was to make a hidden directory containing app bundles of everything, even things that aren’t necessarily GUI apps, and putting that first in the path. This lets Qt find itself, and it has the happy side-effect that I can put a property file inside the bundle that makes those apps not show up in the dock (yay!).
So I’m in the process of uploading new binaries right now. I’ll probably end up not having everything ready for download until tomorrow, since I’m getting about 40k/s and it’s nearly a gig and a half of data. =) From here on out, I suspect the only thing we’ll have to work on for a while . . . → Read More: Fun with App Bundles
Share on Facebook
By RangerRick, on January 20th, 2004%
So it may seem like things are pretty quiet, but actually a lot has been happening behind the scenes. Unfortunately, for now there’s a lot of research that has to be done before noticable progress will happen.
I’ve been looking into how authentication and the keychain work. It seems that kdesu can be replaced with OSX’s authorization framework. KWallet has a pretty nice-looking API that is abstract enough that it appears it should be relatively easy to reimplement the backend portion with calls to OSX’s keychain. Tanner has been looking into the mess that is KKey. It’s currently a twisty maze of x11-specific stuff; it looks like it could be refactored into a very lightweight set of calls to Qt’s key handling. *crosses fingers* I’ve been doing more research into how KDE starts other programs, and their interaction, as well as talking with an Apple engineer on how to get around the issue where fork loses mach ports (and thus the GUI). Benjamin Meyer (aka IceFox) has started a revolution in bringing up getting high-quality versions of the KDE icons for 3.2. He’s also working on building . . . → Read More: KDE/Mac Status
Share on Facebook
By RangerRick, on January 6th, 2004%
I got interviewed by EWeek yesterday. Seems like having KOffice somewhat working is making a lot of waves. =) It’s pretty good, although he got Fink confused (calling it “Think”). Not too big a deal, although our Fink PR dude will probably kill me. Spiffy!
Share on Facebook
Share on Facebook
|
|
|
