<lfam>I have used `guix system vm-image` to create GuixSD virtual machines, but I haven't actually installed in a virtual machine yet
<lfam>quiliro: The only thing about the bare bones config is that it is *really* bare bones. It comes with the editors zile and nano. If you prefer another editor, you should add to the config so that you are comfortable
<lfam>And I do think it's a good idea to test using something like `guix system vm-image` first, because it's much faster than installing to bare metal, and you can cache the binary substitutes between runs
<lfam>That would require you to install Guix on some other GNU / Linux system
<lfam>quiliro: Sorry, I don't know exactly what should be in there. Something is wrong if it doesn't even boot. If you ask again in a little while, there will probably be somebody who can give you better help
<quiliro>the package download was only 1 hour, 3 hours of compilation, the rest was restarting the installation because the installation broke because of server not online for about 1 or 2 seconds
<quiliro>lfam: wikipedia librarians are very rude and impositive....must read the rules because they will ban you and the change will not be accepted
<lfam>Who is going to argue with you? It's not a very big page
<dannym>I've guixsd installed right now. There's /gnu which contains the store. /boot should contain grub (and nothing else). I have a tiny /etc and a tiny /var . /root and /home should exist as usual (if you actually had a "users" form in your config, that is)
<dannym>If there's no /gnu , it didn't work at all
<quiliro>i have nothing of that but configured config.scm correctly....read it 10 times to be sure
<jmarcian`>lfam: if somebody has already put "Linux" and on that page there are so many bias, changing that would incite new arguments and leads nowhere. If someone is editing it already from GNU or GuixSD people, they might make it better, then me who is new to them
<ng_>it's bad that I still need to write some lines, otherwise I could leave for a while
<ng_>hrm. I download the new libressl, I run guix hash on it, I paste it to the file with the changed version, and the hash of the downloaded file when running ./pre-inst-env guix build libressl then is different?
<ng_>it's not even a checkout of anything, just the .tar.gz
<ajgrf>ng_: that happens quite often with github-generated tarballs
<rain1>ring-daemon needs dbus-c++ to build the actual daemon, apart from that it seems like every piece is in place
<roelj>rain1: You have probably already tried, but maybe you could simple install the header files in a normal place with a custom install phase. But heck, it's probably not the last thing that needs to be fixed before it works.
<davexunit>GuixSD will never be a solution for all node programmers. maybe Guix could be a solution for the subset of node programmers that use GNU/Linux, but that still leaves out a ton of people. npm should be better than it is.
<bavier>civodul: I was able to reproduce the guile vm.c failure with -Os, it fails with firstname.lastname@example.org, but works with email@example.com; unfortunately the reduced test-case isn't trivial so doesn't suggest a workaround
<civodul>bavier: oh, ok; so you got a test case generated by c-reduce?
<bavier>civodul: yes, but it's still 7097 bytes in size
<bavier>and since it's not an issue in 5.3.0 it doesn't seem worth a bug report
<ng_>oh, i think I maybe pick advania as a new temporary hoster/dc. I'm just waiting for GuixSD to get where I want it to be, so I can use IN-Berlin with my own server and not worry about bandwidth for the service I used to run.
<lfam>fuzzyhorns: Well, we are biased towards our way :) The Nix paper by Eelco Dolstra is a good introduction to the fundamentals of our system. We are a fork of Nix, although we share very little code.
<davexunit>there's fun stuff like that for a variety of programming languages
<fuzzyhorns>yeah ive read a bit about nix, i should go back and read that paper
<aeva>I'm using guix on fedora at the moment; I did the envirenment --pure thing with the i686 flag as well, now I got a different error, "wineg++ not found" - tried running "guix package -i wine" to reinstall it but said it was already installed?
<efraim>i use links mostly for code snippets, downloading source packages and opening articles from newsbeuter
<lfam>tyngdekraften: Okay, I've never tried that but I have a few recommendations
<mark_weaver>aeva: to be clear, the way this works is that within the "guix environment", every piece of software you use, including the toolchain, will be running in 32-bit mode, e.g. the exact same software I'd run on my 32-bit Thinkpad X60.
<lfam>tyngdekraften: First, be sure to run `guix pull` before you start the `guix system init`. This will update you to the latest package definitions. We have garbage collected the binary substitutes for 0.9.0, so you will have to build almost *everything* from source, and you will not get a bunch of critical security fixes.
<aeva>mark_weaver fedora's version of winemaker just segfaults, yeah, I should probably avoid their build all together
<efraim>hackernews works in links, just missing the formatting for who's replying to who
<tyngdekraften>lfam: Yes, it took almost three hours to compile eveything and the hydra servers were very slow
<lfam>tyngdekraften: Second, we have some very good built-in tools for virtualizing GuixSD in QEMU, under the `guix system` command. For this, you will need to install the Guix package manager on your GNU / Linux distro. This is not hard and does not effect the host distro.
<mark_weaver>aeva: all of the packages you'll need should be included in the 'guix environment' command. guix environment <pkgs1>... --ad-hoc <pkgs2>... will include everything needed to *build* <pkgs1> ..., and will also include <pkgs2>...
<lfam>I really recommend you go that route instead. I do think some users have successfully installed GuixSD in VirtualBox, but I don't have any experience with it
<tyngdekraften>lfam: I can try to built it from in a real system, I just wanted to try it first
<Digitteknohippie>i've long had an idea of gui that teaches commandline/code. are there moves towards interfaces for guix that have this principle that it's easy-for-newbies low bar entry, and without the typical opaque plastic wrap that keeps them ignorant? it seems an idea that fits with the guix philosophy of empowerment, sneaking in code learning through use.
<efraim>i'll have to checkout the ebuilds, I've been looking at the pkgbuilds from arch and the ocassional build script from the BSDs ports
<rekado>yale-haskell looks interesting. It contains some common lisp glue code to provide a more scheme-like environment on different lisp implementations. Much of the code looks a lot like regular scheme code.
<civodul`>rekado: that sounds like a nice project :-)
<ng_>this is in src/autoconf/configure.in which creates the configure-do which is run in the process of configure. however gnu-build-systems seems to not touch line 2885 which includes "CONFIG_SHELL='/bin/sh' " which then causes the build to fail as it produces a #! /bin/sh in configure-do (or -go? idk)