Missing SlackBuilds.org updates
May 4th, 2009
I recognized today that although Slackware takes a huge amount of my freetime, there’s not a single blog entry for it yet. That needed to be changed
I’m aware that there are some scripts on SlackBuilds.org that I maintain and are not quite up-to-date. This has several reasons. First, time is lacking a bit on my side….but that’s not really an excuse since I love working on SlackBuilds. But there are several individual issues currently:
- nvidia-driver
I would really love to update this one, especially after finding out that the current version on SBo (180.29) is capable of damaging certain Fujitsu notebooks. I try every version I can, but anything above 180.29 renders my workstation unusable :/ . I really hate this, especially in this case, but I won’t upgrade to a version that does not work at least on my setup. That being said, at least mentioning the issues of 180.29 in the README would be a good idea.
- virtualbox
Ah, good one. Virtualbox has been driving me crazy the past few days. I finally have working guest additions again and the first thing that happens is VirtualBox crashing. Lovely. Especially after finding out it’s not related to the guest additions at all and keeps crashing on and on and on…. The bug is reported (http://www.virtualbox.org/ticket/3169), was kind of weird seeing it was supposed to be fixed for months now :/
- openerp
This one might still take a while. OpenERP uses quite an amount of new dependencies compared to TinyERP, which are not yet on SBo (at least not all of them). Doing those will certainly take a while, as I use to prefer scripts that are already on there. Of course if the deps would suddenly appear on SBo, things would get speed up quite a bit
- xtuple
Hmm, the next business related script. Unfortunately xtuple is a totally different category as openerp. The build system is the most insane I’ve ever seen. I spent weeks on initially creating those scripts…. Even worse, the developers seem to not care about this issue as I reported it multiple times and all I got was “Thanks. We will keep it in mind for future development”. That, and the fact it’s only working well with 2 year old Qt4 releases makes me kind of pushing it back in the todo-queue….
- pulseaudio
That’s the one I hate most. If I had known what burden it is to maintain it I wouldn’t have submitted it in the first place. I am not going to update this script as long as the current one works with virtualbox (which it does surprisingly well). It does not with every other app I tried. I have stopped asking why…..Of course, if there’s someone with the deep urge to cut off his limbs and head and commit suicide desire to maintain pulseaudio in a way different from the current deep maintainance mode, feel free to drop me a mail
Everything else should see updates soon