After a night of mad hacking, reduz and I (mostly reduz ;) got cheesetracker working!
It's still rough around the edges, and has problems with IT-loading (maybe endianness?) but it works. You can download it here.
June 2003 Archives
CheeseTracker has released a new version. For those who have been following my music troubles, I've been looking for a non-sucky tracker on Mac OS X. Now, not only has he rewritten a lot of the code, he's ported it to use Qt!
That means I can build it with Qt/Mac, and have a native, supported tracker!
Happy day!
Update:
It freakin' built out of the box! Check out some screenshots.
reduz and I are working on putting together a sound driver right now. Hopefully we'll have something soon.
A buddy from work has developed the latest technological advancement in begging technology: e-begging! Can you spare a dime?
I started down the track of getting the latest KDE building with Qt/Mac. I ended up hitting a number of snags, so I'm pretty much stuck until someone more code-savvy than me looks at it (ie, Sam ;)
In the meantime I'm getting the rest of my patches and stuff sent upstream so we're ready. It won't be too long until KDE CVS builds out-of-the-box on Mac OS X (yay!).
As for Qt/Mac, I assure you that as soon as there's something to give you guys, I'll make a note of it here. Just hold your horses a little while longer unless you want to get in on the super-fun porting action... (no, no sarcasm there... <grin>)
Welp, I'm home from my vacation. Of course, you know what the first thing I did when I got home was. I'm building Qt/Mac right now, then I'll look into updating the qt3 dport and start integrating Sam's patches into my KDE stuff.
I'm building with gcc 3.3 just to check things out, can't hurt to be sure everything's clean. Hopefully by the weekend I'll see if I have basic KDE stuff working, and I can start tweaking. Had some thoughts while I was on vacation, I think it would be very cool to have a "desktop2bundle" script or something that will create an application bundle (complete with KDE icon and multi-language support for the label). I'm going to be looking into that once I've got things basically working.
Also saw that my buddy Weave has a blog up now. Looks like he's mostly talking about various mac bits from an engineer's point of view, along with the requisite personal vendetta life has against everything he does. Should be interesting... <grin>
Sam and I have been talking about this for a while. I'm so glad he managed to work things out with TT. Don't suppose anyone wants to sponsor me so I can get to WWDC this year, do ya? :)
In related news, I've been updating the dports to handle building from KDE cvs. Hopefully I'll have something soon, and I can start looking into what it's going to take to get our changes back upstream (again).
Stay tuned for more info!
I just reworked all the PostgreSQL packages for Fink, I'm doing some testing and then I'll release them to unstable. Here's the commit message:
postgresql 7.3.3 -- LOTS of fixes - Fixed postinstall to remove the old entries for "pgsql" (now that the user is "postgres" instead). - Totally reworked the packages to get rid of "postgresql73" (it should safely upgrade over). postgresql73-shlibs and postgresql73-dev (and their SSL counterparts) still exist for compatibility and upgrade reasons, but there's no longer 2 different "PostgreSQL database server" entries for you to decide from. - Perl and Python support has no been properly implemented to do packages for all currently supported versions of each. - Python modules were fixed to build properly as bundles again. This still needs testing from someone with more python-fu. - The SSL packages were re-written by copying the non-SSL ones, so they should be identical except for SSL dependencies and descriptions now. All in all, it's just *much* cleaner. Yay! Now it's time for some deep testing, then release to unstable.
If you're feeling adventurous, please try them out!
Watch out for an update to KDE tonight, I'm moving KDE 3.1.2 to stable. If you have problems (other than FT_New_Face symbol issues, which are out of my hand), let me know...
(This is a repost of my post to OSNews.)
I'm one of the core Fink maintainers and I also maintain some packages (and have even recently done some development) on darwinports, so I hope I at least have a little bit to say about this. ;)
A lot of the comments are saying "why?!?!" Really people, you should know the answer by now. "Why not?" It's a fun hack, it's neat, it's satisfying when you accomplish it. Who needs another reason? If other people get something out of it, great.
As for "what this means", it means another infrastructure for porting packages. Yes, they're duplicating functionality... I made the same complaints when darwinports started out, but darwinports has done some pretty innovative things and has great plans for the future; I've since decided I no longer have the right to ask why -- it's not my place.
You'll find that the "packaging" (ie, making the package description) is the easy part. "Porting" is the hard part, and there is very little overlap in that space. A number of fink and darwinports developers hang out in each other's irc channels, and there's a lot of code-sharing that goes on patch-wise between the two. I maintain two sets of identical KDE packages, one in each, the only difference being how it's packaged up. I see no reason things won't work out that way with Gentoo in the mix too.
People really need to stop whining about what does what and instead just go with what they like. If we're all doing our jobs, very little overlap happens. Each system has it's own advantages. Fink is very stable and has the largest number of packages. Darwinports is more bleeding-edge, but also supports "pure darwin" and darwin/x86 where in many cases Fink does not. Portage just adds another bit to the mix. I expect the most likely reason to choose portage over Fink or dports is for bleeding-edge and maybe custom compilation flags, but it remains to be seen how well that works.
In general, darwin is still a 2nd-class OS as far as support for "out-of-the-box" building. The Gentoo folks will find they need a lot more patches to make things play nice on darwin than for Linux, so some of the "immediate update"ness of gentoo may not happen on darwin just because someone will have to actively fix patches on each release of a port.
All in all, chill out people. If one of these packaging systems isn't "good enough", it will die out on it's own. Darwinism (excuse the pun) will win out in the end. Otherwise, use what you like; I assure you, you won't be hurting my feelings. :)
Shantonu Sen and I have been working a lot on RPM, and the RPM port in dports. Things are looking pretty good now, I'm doing enough building to have a mock-up of a yum repository (kind of like apt) up and working.
I've got 10 or 12 packages for both ppc and x86 built, and all seems to be going well so far. Feel free to give it a shot and give us feedback, it's starting to look pretty slick!
