Apparently if you go through all the trouble of typing that one command: sudo port install amarok-devel, amarok trunk will be thine.
Why don't these things ever work so well for me? Don't I deserve it?
As things seem to be working I'll update normal amarok to 2.1.1. Someone should tell me if it works since for me, it'll probably not work without some haxxxing. You know, because I don't deserve it.
I wonder if it's because I'm getting an android phone...
Do they know?
The KDE group of portfiles've been updated to 4.2.4. This might fix the massive breakage that occured when the 4.2.0 tarballs disappeared into the InterEther months ago. Or not.
Some other changes are the addition of liblastfm, taglib-extras and qtscriptgenerator. That's right, everything you need to get your bleeding edge fix of amarok. Except amarok itself.
Installing it requires stuff I'm not going to put in a portfile because Saturday's pretty much done and I've already got it working for me. Muahahahahahahahahahahahaahaaaaaaaaaah.
The following pertains to Aaron's blog post. It is in direct response to this sentence That means you'll look and work native on Windows, Mac, KDE and GNOME if you write using Qt.
To which I replied via comment.
NO. NO. NO. NO. NO.
I've said it once and I'll say it a thousand more times: Qt does not look native on Mac OS X.
As a matter of fact it currently (4.5) looks like the bastard step-child of 10.3, 4, 5, and something else.
A while ago I started a countdown to I didn't know exactly what. I just felt like doing it. It was expected that as I got closer to the time that I'd know what exactly it was that I had been counting down to. Turns out I was right :-) And also wrong. I thought maybe the countdown would have been an announcement that I'm going back to school. Graduate School. Again. I'm already back however and have almost survived one full quarter. As the time has gotten closer I have been ...
illogic-al.Org