February 2004 Archives

Well, I'm back from vacation and ready to pick up some of the threads I was working on before I left.

Big things on the plate right now:

1. Either package XFree86 4.4 final or backport Darwin-specific fixes to the 4.4 rc2 released before the recent licensing fiasco, depending on how we want Fink to handle such things. I have to do some looking into it first.
2. Get the KDE/Mac stuff up-to-date with latest CVS and make sure all the patches are cleaned up to start tinkering again.
3. Finish up fixing some upgrade issues with certain KDE/X11 Fink 3.1.x -> 3.2 transitions.
4. ??
5. Profit!

Been quiet, hasn't it?

Missing you in the Carribbean. Oh, wait, who am I kidding. =)

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 need to update your package listings, by doing:

fink selfupdate

You must have unstable enabled, and be configured to pull packages through CVS or RSync, not just updating at "point release". If you are currently tracking point releases, you can run "fink selfupdate-rsync" (preferred) or "fink selfupdate-cvs".

For more information on enabling unstable, see:

http://fink.sourceforge.net/doc/users-guide/conf.php#optional

Once you have a fresh package listing, you can update by running "fink update-all" if you have an existing KDE installation. If you did not previously have KDE installed, you can run "fink install bundle-kde-ssl" (or "fink install bundle-kde" if US export laws prevent you using strong crypto).

Problems? Questions?

If you have questions or problems, please try the Fink mailing lists:

Fink Beginners: http://www.finkproject.org/lists/fink-beginners.php
Fink Users: http://www.finkproject.org/lists/fink-users.php

Or, you can contact the maintainer (me).

I expect there will probably be some upgrade issues, I've done a lot of testing of the 3.2 series from prerelease on, but things always pop up. I will do my best to get things fixed up as soon as possible.

So I ended up delaying the KDE release, it turns out there were some major problems in handling freetype. I've reworked the way I do builds (and, it turns out, made it quite a bit easier to manage while I was at it), and am doing testing right now. Hopefully I'll finish up the builds sometime tomorrow and be able to release, things are looking good now.

*crosses fingers*

So at work we're doing this sales thing where if you refer someone, you can win an iPod. If you know someone who might be interested in a network management appliance, please fill this out. You may win an iPod, whoever buys an OpticNerve will get an iPod, and I might get an iPod. Everyone wins! =)

Looks like I didn't get the Fink packages ready in time. =)

I've still got a few dep bits to clean up, and some upgrade testing to do, so it looks like the packages won't be ready until probably wednesday or thursday (more likely thursday).

Ah well, I was close...

On the bright side, it takes so long for people to build KDE that I won't get bug reports until the weekend. <grin>

Just a quick update, the KDE builds have been going well, I've been doing a bunch of cleanup on the info files, and making scripts to make it easier to manage 10.2-gcc3.3 and 10.3 concurrently (I actually generate the info files from a "common" set.) I'll probably be all finished up this weekend, and will be ready for a release along with the source, if things continue as they are. (yay)

And so, I'll leave you with this:

<RangerRick> now I know... uhh... a mac address
<Sortova> sshh
<Sortova> Everyone will want one

[Update:] Made more progress over the weekend, all that's left to do is make sure upgrading over the previous binaries works, and clean up some new dependencies, and I'm set. I also think I've fixed Qt so it works better with qmake projects.