IRC channel logs

<zacts>hello!

<zacts>night and day, you are the one. beneath the sky and under the sun.. - cole porter

<jmd>warning: while fetching http://hydra.gnu.org/2grfjpn4w3b28q0066fx596ry2rpdfnd.narinfo: server is unresponsive

<civodul>Hello Guix!

<civodul>jmd: i'm processing your patches :-)

<jmd>Ok. Thanks.

<jmd>These packages which depend upon themselves are rather nasty.

<jmd>I wonder if it might be a good idea to split them into two or more outputs.

<civodul>no, i think that's OK

<civodul>those that depend on themselves for cross-compilation you mean, right?

<jmd>Yes.

<civodul>so yes, that's fine

<civodul>oh the big patch entail glib/python/dbus rebuilds...

<civodul>well, that's fine i guess

<handheldCar>I tried to build zsh in a virtual machine, but the virtual machine gave me so many issues that I quit. (I need another PC)

<civodul>you wrote a package definition for it?

<handheldCar>no, would that help?

<civodul>actually, if you're using gnu-system-demo-0.5, you need -m 1024 or so if you want to use 'guix pull' or the substituter

<civodul>handheldCar: dunno, i was trying to understand what you were saying :-)

<handheldCar>wasn't running well. maybe your demo will run smoother.

<civodul>what virtual machine did you use? how did you try to build zsh?

<handheldCar>I used virtual machine gnewsense. default gateway was missing, lots of buttons would register ten times after I pressed them: exampleeeeeeeee.

<handheldCar>virtualbox I mean

<civodul>oh ok

<civodul>how does this related to Guix? :-)

<civodul>*relate

<handheldCar>unrelated

<jmd>civodul: Have you thought about how to handle those autoconf tests which can only be resolved at run time?

<civodul>connection lost

IRC channel logs

2013-12-15.log