IRC channel logs
2014-03-21.log
back to list of logs
<mdh`>guix people, i started porting guix to osx ... i dunno what the interest level is on this topic, but ... <mdh`>i got the make install to complete, ran a guix-daemon and issued <mdh`>~/guixinstall/bin/guix package --install=dmd <mdh`>ERROR: In procedure scm-error: <mdh`>ERROR: bootstrap binary not found "tar" "x86_64-darwin13.1.0" <zacts>mdh`: I would be interested, possibly in using guix in a project of mine NuBSD at #nubsd on freenode <zacts>but only if you get guix to work on another platform. <mdh`>yeah, all very interesting ... personally i don't even know why i'm porting it for osx, it's one very cool hunk of scheme i guess <mdh`>i think it would be sweet on top of a netbsd kernel <mdh`>but just the base project is a wonderful cause too <zacts>mdh`: yeah, I don't know if I'll have the time to actually do it, I'll probably focus most of my time on the core guix. <zacts>mdh`: although we hope to have an iso w/o ports ready by July of this year <zacts>for NuBSD Fire (based on FreeBSD) <zacts>so you could at least utilize jails / pf / bhyve (ultra high-speed virtualization) <zacts>we aim to be compatible with the fsf guidelines for a free distro <zacts>and possibly debian's also, but fsf is top priority <mark_weaver>mdh`: I think we're not interested in porting guix to non-GNU userland, but fwiw you need to read the porting section of the manual. <zacts>mark_weaver: totally, yeah. this would only be a personal off-topic project to port guix to a non-gnu userland <zacts>(as far as NuBSD is concerned) <mark_weaver>well, I think you underestimate the difficulty, but have fun :) <zacts>mark_weaver: I would probably work more towards a gnu/kNuBSDFire project before I would do that. <zacts>yeah, I don't think I have the time for several years for that, and also once I get NuBSD Fire iso released, I won't be contributing most of my time to that project, I'll focus more on out-of-box gnu guix gnu/linux. <zacts>My main personal goal with that project was to get a base iso ready that can virtualize gnu/linux / jails / pf firewall. <mdh`>yeah, all makes sense. no desire for any non-GNU impurity! <mdh`>and there's a heap of work i imagine in just getting the coveted iso delivered <civodul>kindahero: will you be available full time during GSoC? <civodul>kindahero: so no classes and no other job during the summer? <kindahero>I have no classes, but during the day time I will be busy with research work. <kindahero>I am not a CS student. But I do code every day for research (mainly <mark_weaver>civodul: should I avoid updating from nix-upstream on MIPS, for lack of KVM? <civodul>mark_weaver: the daemon just bind-mounts /dev/kvm, but it doesn't use it <civodul>so you can just "touch /dev/kvm" and it'll be happy :-) <civodul>kindahero: sounds hard to handle 3 different kinds of jobs concurrently <civodul>at any rate, make sure to submit your proposal on Melange today <phant0mas>mark_weaver: how can I say if target or current system is i686-pc-gnu return glibc/hurd else return glibc/linux? <phant0mas>I was thinking something like (cond ((string-match "i686-pc-gnu" target) '()) (else '()))) <mark_weaver>phant0mas: well, the string comparison can be done with just 'string=?', or better yet use 'match' from (ice-9 match): (match target ("i686-pc-gnu" glibc/hurd) (_ glibc/linux)) <mark_weaver>however, I'm not really sure about the other question of how to make the 'glibc' be bound to one or the other, without making 'glibc' a procedure that returns a package, instead of just a package. <mark_weaver>you'll have to ask civodul what he had in mind there. I don't have time right now to think about it. <bavier>just an FYI, I'm looking at packaging midnight commander, but getting some compilation errors, so might take a little longer than hoped...