By RangerRick, on February 29th, 2004%
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:
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. Get the KDE/Mac stuff up-to-date with latest CVS and make sure all the patches are cleaned up to start tinkering again. Finish up fixing some upgrade issues with certain KDE/X11 Fink 3.1.x -> 3.2 transitions. ?? Profit! 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 February 6th, 2004%
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*
Share on Facebook
Share on Facebook
By RangerRick, on February 3rd, 2004%
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>
Share on Facebook
Share on Facebook
By RangerRick, on February 2nd, 2004%
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.
Share on Facebook
Share on Facebook
By RangerRick, on January 27th, 2004%
Unless showstopper bugs are found, the tarballs released to packagers will be KDE 3.2.0 final (feature plan). I’m taking a break from working on KDE/Mac stuff long enough to get final Fink packages put together. I’ve got up to kdebase built and I’ll be continuing getting things cleaned up in preparation for release. If I’m lucky, I’ll be able to do a simultaneous release of the info files with the tarballs. If not, well, it won’t be too much later. =)
Share on Facebook
Share on Facebook
By RangerRick, on January 27th, 2004%
So there’s this big thread on the Apple SciTech list about Fink which seems to be complaining about a number of things that are either design features that people don’t understand, or outright FUD about things that Fink supposedly breaks that has nothing to do with Fink.
For example, in this post, he says:
Be aware that if you link against Fink libraries, you are not writing code for MacOS X. You are writing code for Fink. The resulting code will not run on a vanilla MacOS X system, which in my humble view is a ‘really bad idea’ (TM).
There’s nothing wrong with linking against Fink libraries. If you want to include them in your own project, you can use install_name_tool to relocate the library for use in your own projects so that you don’t need to work with the /sw directory yourself. The problem happens when you don’t do this (e.g. Virex installing libs in /sw!). This is not Fink’s problem, this is a problem with not understanding the Mac OS X development environment, and how library paths work on Darwin.
If you can’t just . . . → Read More: Misconceptions about Fink
Share on Facebook
By RangerRick, on December 11th, 2003%
Been working on doing test builds of the Gnome 2.4 stuff and looking for missing build dependencies; it’s starting to look *really* good. All of the major bugs seem to be worked out, only a few minor things until it’s releasable, if I had to bet. Also, I’ve made a newer xfree86 snapshot. If you’re running unstable on 10.3, you should be able to “fink install xfree86” after a selfupdate and get 4.3.99.901-2. This is roughly equivalent to the 4.4 release candidate that Torrey announced, although it’s a slightly newer CVS snapshot. Please let me know if you run into any problems with it, initial testing shows it to be pretty stable on my system.
Share on Facebook
Share on Facebook
By RangerRick, on December 3rd, 2003%
Yes, I’m still working on KDE 3.2 beta packages for Fink. 3.1.94 (beta 2) just went to packagers and it’s looking a *lot* cleaner than beta 1 was.
So of my previous TODO list, here’s where I’m at:
aRts works again (thanks, Justin, for remembering we’d patched the esound driver ourselves, previously!) KDevelop builds and works great on 10.3. On 10.2-gcc3.3, it has some issues because it appears exceptions are seriously screwed on the gcc 3.3 that you can get for Jaguar. Ada, Java, and I think a few others will have to be disabled. Other than that, it appears to be looking pretty good. KOffice is the last thing I need to dig into, but that’s not in Fink right now anyways, so nothing’s stopping me from releasing the rest of KDE right away.
I’ll post a note here when I’ve got 3.1.94 ready for release; I expect just a few more days if nothing goes wrong. Cross your fingers!
Share on Facebook
Share on Facebook
By RangerRick, on November 25th, 2003%
You may or may not have known, but Fink is GPL’d. There are certain legal obligations that must be observed when you use GPL’d software. There are also certain cultural obligations that, while they don’t have to be observed, really should be if you don’t want to piss people off. I’ve got no problem with the fact that OpenOSX repackages Fink. Under the GPL they’re allowed to. On the other hand, I find it pretty rude to not even mention the fact that they’re doing so. I wouldn’t have given this much thought but OpenOSX came up on IRC today. Someone mentioned their recent release of their “GIMP 2.0 prerelease” on VersionTracker (as well as lying about their GIMP’s capabilities). Sure, it’s not illegal, but when someone else is charging money for work that I and hundreds of other developers are doing, usually in their spare time, it rather pisses me off. I’d happily forgotten about OpenOSX until it was brought up again on IRC; now I’ve gotten mad all over again. I’m not the only one, our previous head of Fink (who, incidentally left after feeling unappreciated for too long) put a similar . . . → Read More: Sometimes the GPL is Not Enough
Share on Facebook
|
|
|
