illogic-al.Org

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 ...

I feel like I should blog about something but have nothing particularly compelling to say. As that's never stopped me before, and for no other reason than it's the end of the month and my sidebar tell me I have no entries for May, I'll do it anyway. Time to retreat to the good ol' standard then: Bitch, bitch, moan. You were warned.

http://stufffchristianslike.blogspot.com/2009/04/532-arguing-about-why-b...
so nice, I had to talk about it twice (today)

Prologue
So I've been attempting to read the Bible, the whole Bible, for years now. It's a remarkably boring prospect though. Call me sacrilegious if you will but that is honestly how I felt and sometimes still feel about it. I believe if you're honest you may just admit the same.

On my running system, from a fresh log in, KDE reveals 1268876 K memory usage in GNOME vs. 1279348 K memory usage in KDE 4. That is a change of 10472 K. Granted, this is not a huge difference.

This was taken from an article which I won't bother linking to. It doesn't need anymore traffic. I just thought I point something out as it's Saturday, I'm bored and I had a long day in the lab yesterday and need to vent and for some reason the previous quote from an article which shall remain nameless just annoyed me.
Perhaps I woke up cranky. *ahem*

Howdy do all you out there in interland. This one is mostly for A. L. to get her to stop pouting.
Today, boys and girls, I'll be speaking about macports. Macports is a ports-like package management thing for OS X. For all my arch linux peeps, it's like the AUR for PKGBUILDs, but you need privileges to check in. It's both easy to use and easy to break. Er, easy to contribute to I meant. These contributions are known as Portfiles; text files defining various things necessary to compile your software of interest.

NetBible version:

14 Bless those who persecute you, bless and do not curse. 15 Rejoice with those who rejoice, weep with those who weep. 16 Live in harmony with one another; do not be haughty but associate with the lowly. Do not be conceited. 17 Do not repay anyone evil for evil; consider what is good before all people. 18 If possible, so far as it depends on you, live peaceably with all people. 19 Do not avenge yourselves, dear friends, but give place to God's wrath, for it is written, "Vengeance is mine, I will repay," says the Lord. 20 Rather, if your enemy is hungry, feed him; if he is thirsty, give him a drink; for in doing this you will be heaping burning coals on his head. 21 Do not be overcome by evil, but overcome evil with good.

That compiling cocoa and qt3support in Qt 4.5 at the same time isn't possible. Yip. Currently Amarok 2 and kdegames are only things that don't crash when KDE is run with qt 4.5 + cocoa. Maybe Dolphin too.
That's all. Back to butchering the kde-mac site.

Make kde compile in macports in 10.4

Index: kde4-1.0.tcl
===================================================================
--- kde4-1.0.tcl (revision 47836)
+++ kde4-1.0.tcl (working copy)
@@ -31,31 +31,49 @@
# Use CMake Portgroup
PortGroup cmake 1.0

+# Pull in automoc build dependency. Needed by most/all KDE software.
depends_build-append port:automoc

+# Turn on parallel builds.
use_parallel_build yes

+# Create out of source build which KDE requires (and enforces).
worksrcdir build

I was just thinking about all the projects I've contributed code to in the past and thinking, "Huh. That's quite a sizeable list."
The list goes something like this:

• Enlightenment (0.16-ish)
• Kicker
• Amarok
• Konversation
• Qt
• Kopete
• Macports
• Openbox (3-ish)
• KDE (4.2-ish)

'sudo port sync' then 'sudo port install/upgrade koffice-devel' to join the fun.
That is all.

I was going through stuff on my old macbook pro drive and I found this cover letter I wrote some time last year (possibly this time last year). I believe I sent it out in a form very similar, if not identical to what you'll see below. I don't remember why, but I was quite serious and if I'm not mistaken, someone from Cornell did call me for a phone interview. Just goes to show boys and girls, honesty ain't gonna kill yah (then again, no guarantees that it wont ...).