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:
Home again! Preparing to go to sleep by Bleach (not Beach) and I just thought I'd say Hi
:-). I saw a frozen lake while flying over St. Louis today. It was beautiful. Pretty mellow and that's how the rest of the day went. It was a welcome departure from Friday night/Saturday morning; rushing from Terminal to Terminal @ JFK, AirTrain hopping betwixt said Terminals, then running to catch a bus to LaGuardia. In retrospect the detour to my Mom in NY was, perhaps, not the best thing to do.
Being only one post away from breaking my "most posts in a month record" and somewhat making up for the dearth is posting last month, I present to you "Taming the Tiger!". Er, Leopard that is.
This January, God willing and KDE E.V. paying, I'll be in Jamaica for the 1st (hopefully) annual Camp KDE conference. Camp KDE spun out of the KDE 4.0 release event which took place in Mountain View, Cali at Google's place. Legend has it the organizers of the event realized that there were a lot of people who weren't going to the akademies in Europe because they a) couldn't afford it b) had other engangements at that time. I can relate to both points as I was always either in school whenever they had akademy (scheduled too close to end of semester/exam season) or couldn't afford to go.
When last we spoke I left on a rather uncertain note. But will it work...
I asked. The immediate answer to that query was No. It will not.
Being far too persistent with these things I kept on working until the answer was Yes. I have defeated you, vile beast.
Yes, dramatic. I know.
What do you do after working on something for 16 hours? Take a break. A long break. For 4 hours on Friday and 12 straight hours on Saturday I was working on getting my installer package ready. The installer package in question had precious paylod: a beta version of Amarok 2. I finally got it in a state I was comfortable with and released it into the wild. It took quite a bit of work, far more than expected, to get the installer working to my satisfaction. There were some things which I required it to do, or not do, before I was comfortable with releasing it; things which I list below.
Make what so? OS X packages of course! This weekend (actually Labor Day for all us Yanks) a little rose pricked me and reminded me about those packages I was supposed to be making. The friendly poke gave me the activation energy needed to get over the hurdle and get the job started again. That's a little in-joke for the Chem geeks in attendance.
After having a talk with aseigo today I have been lulled out of my ill-deserved slumber. So let's try something and see where this goes...
Plan -
Step 1:
Collate an actual list of all KDE's dependencies (Techbase).
Step 2:
Find out which are actually used for functionality on OS X (libagg, opengl).
Step 3. Remove or otherwise move out of the way X11 includes and libraries.
Step 4: Compile and package software only requirements software provided by the base the operating system. Qt first.
Step 5: Repeat Step 4 for the kdesupport software from a stable snapshot.
So the boss wants me to design some siRNAs, the uncle wants me to create an email account and do other resumé related tasks. This is while I want to figure out if I can get phonon-qt7 to load files via kioslaves. Let's not forget that I have to get utilities and insurance set up for the new apartment. Apparently I'm a miracle worker because this was sprung on me Wednesday and ideally needs to get done before Friday. Did I mention that I actually officially start work on Monday, not Friday?
I bought a new macbook this weekend because: a) I wanted one, b) I didn't want to wait for Apple's notebook reload and, c) I've become increasingly frustrated by the long compilation times with my (2 year) old Macbook Pro. The good news is its faster, the bad: I don't like it.
illogic-al.Org