IRC channel logs
2013-08-30.log
back to list of logs
<Fulax>well, the documentation says that guile-2.0.7.tar.xz is part of the source distribution *Fulax hates when running 'make' <Fulax>downloads things on the internet <gazoombo>hi, I'm going to have to duck out shortly, but I thought I'd pose this question first: can guix be successfully bootstrapted from Debian Wheezy (stable) without additional experimental packages? <gazoombo>right now I'm getting this when running ./bootstrap from git HEAD: ... <gazoombo>configure.ac:9: require Automake 1.12, but have 1.11.6 <gazoombo>autoreconf: automake failed with exit status: 1 <mark_weaver>if you build from the 0.3 tarball, you don't need automake <mark_weaver>yes, you should be able to build the tarball on wheezy without any experimental packages. <mark_weaver>alternatively, you can install automake from experimental. <mark_weaver>(which I did on my wheezy system, and it's very unobtrusive) *Fulax watches the video linked by civodul a few hours ago <mark_weaver>civodul: I watched your presentation on Guix. Am I right in assuming that your queries about 'syntax-session-id' are about trying to ensure that builds are always bit-for-bit identical, as opposed to "almost" identical? <mark_weaver>I've been thinking it over some more, and when compiling normal guile modules, it should be sufficient to use a 'syntax-session-id' that's derived from the module name. <mark_weaver>where it gets trickier is when something's being compiled that not a normal module. <civodul>mark_weaver: yes, that's the "fixed point project" <civodul>i was thinking something along these lines, but i haven't taken the time to investigate <civodul>(and it turns out to be in fashion, it seems) <mark_weaver>not surprising, given the relevations of edward snowden. <mark_weaver>well, I'll make a serious effort to find the best solution we can. <mark_weaver>the really hard part is what to do when something like "primitive-eval" is called. <civodul>in that case we can always resort to a random thing <civodul>that won't end up in .go files, so that's OK anyway <mark_weaver>what about 'load'? do you think that's likely to be a problem as well? <civodul>i guess the issue is what to do when the current module is the-scm-module <civodul>i'll have to disagree on that one ;-)