<reepca>... I just realized something. How am I supposed to copy the output from a build using call-with-container to the store? I can't copy it from outside because I have no way of knowing where the temp directory is, and even if I did, it would be automatically deleted by the time control returned. And I can't copy it from inside because it's inside the container.
<solene>I have a T400 which is compatible. I tried this morning to install guix on my work laptop with the ISO you provided me, it boot, I can type commands but guix system init fails in the middle of the process and can't be started again, I trid with differents config, removing things up to have the same config as bare-bone without success.
<lfam>Thanks solene, I'll work on fixing those links
<solene>now that I made "./bootstrap && ./configure --localstatedir=/var && make" is it safe to use sudo make install ?
<lfam>I would do `make check` before installing, but otherwise it should be fine.
<solene>if I want to create new packages, do I need to recompile everything each time I modify the definitions ?
<lfam>If you don't run `make` to recompile, Guile will recompile on the fly, but not store the result of the build on disk.
<lfam>But, the Guix you install is not the Guix that is consulted for package definitions, if I understand correctly.
<solene>maybe I doing it wrong. I would like to learn to make packages for guix, so I assume I need to work from the git repo ?
<solene>can't I merge the guix of guixSD with the one of the git repo ?
<lfam>The Guix you install is what you run when you do `guix build` or `guix package`, and it contains the guix-daemon you typically use. But, the Guix that provides package definitions and related things is normally found through a symlink at '~/.config/guix/latest'. That is what is updated by `guix pull`.
<lfam>If you just want to use your changes to the Guix source, I recommend using the 'pre-inst-env' script that is created when you build Guix from source.
<lfam>For example, you update the version and hash of a package and want to try it out. Use `./pre-inst-env guix environment --ad-hoc foo`
<lfam>That 'pre-inst-env' script sets everything up for you
<solene>and after typing pre-inst-env, I can do "guix package -i mypackage" ?
<lfam>It's a single command. The pre-inst-env script changes some environment variables for `guix package`
<lfam>I don't recommend using `guix package` for testing changes, though. All the testing versions of the packages will end up in your profile history. That's why I recommend `guix environment --ad-hoc` for this use case
<solene>lfam: how do I try a package I'm adding if I don't install it ?
<Ivanhercaz>I have install GuixSD 0.13 but when the process finished I get an error installing grub. I restarted and when it init it didn't load any grub (and in the boot only appears the entry for "ubuntu", because the last operative system was Elementary, but now it is broken and appear a console with GNU Grub version 2.02