Short sta­tus: RealPlay­er, Sound, Lin­ux, …

I’m busy with non-FreeB­SD relat­ed stuff since a while, so there’s not much to say.

RealPlay­er: Shaun, the FreeB­SD main­tain­er of the helix­play­er port, promised to pol­ish up a patch­set when he gets time to port helix­play­er to a more recent ver­sion and send it to the cor­re­spond­ing helix com­mu­ni­ty (request­ed by some peo­ple at Real after show­ing them the patch­es via cvsweb). Their review and inte­gra­tion of this stuff will help in get­ting a RealPlay­er bina­ry from Real.

Sound: The work of Ariff (and every oth­er con­trib­u­tor) in the HDA area seems to be very appre­ci­at­ed. There are aven voic­es ask­ing for a MFC. I don’t think we will get it for 6.2. It’s too late in the release process and Ariff seems to be busy.

Sound2: Ryan com­mit­ted a fix to P4 which should pro­vide some miss­ing stuff to some break­ing ports. If some­one has time to com­mit it…

Lin­ux: A lot of progress hap­pened here. The long­stand­ing major bug on amd64 is fixed and MFCed (thanks to kib!), so we final­ly got some results for the amd64 runs of the LTP test­cas­es (now col­or cod­ed to spot prob­lems much faster). The sta­tus of the sta­ble run is already on the wiki page (but this is with­out the MFC). Runs on cur­rent (2.4.2 and 2.6.16 based emu­la­tion) and sta­ble after the MFC where already done, but I did­n’t got time to wiki-fy their sta­tus yet.

Ports: I already have an update for my sylpheed-claws port to 2.6.0 togeth­er with a move to LOCALBASE (includ­ing the plu­g­in ports) avail­able, but I have to wait until the ports-slush is lift­ed.

Send to Kin­dle


Since Roman want­ed to cre­ate his lin­ux­o­la­tor branch in per­force, I had to make myself famil­iar with per­force too, to be able to answer his ques­tions. I learned my first steps in per­force by cre­at­ing the sound branch (I’m men­tor­ing Ryan togeth­er with Ariff). Cre­at­ing the branch was not hard, but I man­aged to fail in some way… I used the wrong user­name part for Ryan’s branch name (“rbeasley” instead of “ryanb”). I think this means I should­n’t trust my mem­o­ry and double-check such facts in the future. Since it’s only a name­space issue to not have con­flicts when sev­er­al peo­ple want to cre­ate branch­es with the same name (but a dif­fer­ent seman­tic of what has to be done there), I don’t think it mat­ters.

Roman had­n’t as much “luck” than I had. He for­got to add a ‘/’ in an impor­tant place which result­ed in files like “…_linuxolatoramd64/…” instead of “…_linuxolator/amd64/…” while branch­ing. While ICQ is nice to dis­cuss some­thing in real-time over large dis­tances, you can’t look over the shoul­der of some­one. Mea cul­pa (stu­dents which are excit­ed and eager to try some­thing… I think I remem­ber how this feels 😉 ). He is resolv­ing this as I write this.

While I see some ben­e­fits in the way per­force is work­ing (seems to allow some pow­er­ful things we can’t do with CVS), I have to say the per­for­mance sucks when cre­at­ing branch­es (I did it at home via DSL and a com­pressed ssh tun­nel to the per­force serv­er, not on freefall where it should have been much faster). But I did­n’t cre­at­ed a FreeB­SD branch with CVS, so maybe CVS sucks more when doing this. 🙂

Send to Kin­dle