after a multitude of (highly unsuccessful) attempts to compile and install kde 4 from source using the directions at techbase (everything would build fine, but i would encounter strange errors upon login and plasma was broken), i finally decided to format an i686 machine i had kicking around with arch and install the kdemod4 testing packages.
February, 2008
introducing megaman: and not the one you're thinking of.
if you use arch linux, then chances are you've become accustomed to relying on the command line for package management. pacman is, after all, a very robust and powerful package manager, and definitely one of the distribution's strongest features. unfortunately, it also lacks decent gui frontends. i'm new to arch and the first thing i found is that most of the current frontends to pacman are either discontinued or highly confusing, so i've decided to take matters into my own hands.
easing into a much-needed march break.
i woke up in freeport this morning and am now typing this from a house just outside of orlando. my internal clock is offset by three hours of flight and close to ten hours of driving in the past day and a half (something that most people in this world could eat for breakfast,) but i'm not used to all the travel, especially after becoming habituated to the residence lifestyle. sleep will undoubtedly wear it off, and tomorrow is a new day, but for tonight i have some thoughts, and i apologize for the broken flow of words to follow.
a renewed appreciation for mozilla devs.
so i've jumped on the mozilla thunderbird bandwagon, but it's common knowledge that the client doesn't provide a whole lot out-of-the-box. pop/imap monitoring and an address book aren't of much use to me by themselves in a standalone application, especially after my (sigh) extensive experience with microsoft's outlook. what i've quickly learned, though, is that the biggest mistake anyone can make after installing (firefox or thunderbird) is to accept the default configuration as the one-and-only way of doing things.