IRC channel logs
2013-12-25.log
back to list of logs
<gzg>zacts: It's pretty easy on wheezy, but unless you custom compile Guile 2.0.9, Guix complains when grabbing sources. *gzg is on Testing on his main laptop now (plans to, until upstream GNU is usable) and it's not a problem. <gzg>mark_weaver: Fyi, I finally tried your vm generation expression "./pre-inst-env guix build -e '(@ (gnu system vm) system-qemu-image (@@ (gnu system vm) %demo-operating-system) #:disk-image-size (* 1.5 (expt 2 30)))'" -- and it doesn't seem to work. :^P *gzg is currently working on getting resize2fs working in the vm. <mark_weaver>"./pre-inst-env guix build -e '((@ (gnu system vm) system-qemu-image) (@@ (gnu system vm) %demo-operating-system) #:disk-image-size (* 1.5 (expt 2 30)))'" <mark_weaver>(missing set of parens around the module reference to system-qemu-image <mark_weaver>alternatively, you could just hack your copy of vm.scm <mark_weaver>git is quite good at managing your local changes and merging upstream changes back into your copy. <mark_weaver>(or rebasing your changes on top of current upstream) <gzg>mark_weaver: If I just hack vm.scm, after I reload the module -- would I just "guix build vm", I assume? <gzg>mark_weaver: On the mailing list, or? <mark_weaver>"./pre-inst-env guix build -e '((@ (gnu system vm) system-qemu-image))'" I think? <zacts>gzg: I wonder if I can just bootstrap an earlier guix, and then update that way to the latest git.. (rather than having to install guile from source manually). <gzg>It complains "gnu/system/vm.scm:444:2: In procedure #<procedure 1d72150 at gnu/system/vm.scm:444:2 (store)>: <gzg>gnu/system/vm.scm:444:2: Wrong number of arguments to #<procedure 1d72150 at gnu/system/vm.scm:444:2 (store)>" <zacts>I remember I had other problems also, the last time I tried it.. <mark_weaver>zacts: installing guile from source is pretty easy on wheezy. just "sudo apt-get build-dep guile-2.0" which takes care of the dependencies, and then grab the 2.0.9 tarball. <zacts>I know, but I for some reason had other problems also. <zacts>hm.., well let me try again, I must have made a mistake or something.. <mark_weaver>if you install guile in /usr/local, and make sure to run "sudo ldconfig" after "make install", with the default debian configuration it should be fine. that's how I've always done it anyway. <mark_weaver>removing the guile 2.0.5 packages is probably also wise. <mark_weaver>(it probably shouldn't be necessary, but I don't remember the last time I had the 2.0.5 packages installed) <zacts>oh, cool. I didn't do sudo ldconfig after make install <zacts>I'll try it in a few minutes.. <mark_weaver>ah yes, that's always needed when installing a shared library outside of a package manager. <gzg>Build-scripts/profiles, I think will be very cool -- eventually. :^) *gzg still needs to package like ~10 things before 1.0 -- after that, he thinks he could be ready for upstream GNU full-time. Besides any big DEs, I wonder if there are any really big packages needed that would hold one back from switching over. <zerwas>Is there some sort of end-user documentation for Guix? <zerwas>Steap: thanks :-). The reference manual still very technical and verbose <Steap>zerwas: you should read the autotools documentation :) <zerwas>On page 4, copy-paste does not work because it uses ` instead of ' <jmd>zerwas: What do you mean "does not work" ? <jmd>Actually IMO the manual is not verbose enough. <jmd>But I agree that it is rather technical and not really aimed at the end user. <zerwas>Oh, nevermind. It is only malformatted in the PDF version. The HTML version is correct <zerwas>Will I need to set any other variables other than $PATH, $MANPATH and $LD_LIBRARY_PATH? <zerwas>I see $HOME/.guix-profile/man, so I guess it's necessary