@dthompson It seems very interesting, but how do you...

@dthompson It seems very interesting, but how do you run the example? I tried this:

$ LANG=en_US.UTF-8 guix shell -f manifest.scm -- make
[/…]/guile-hoot/examples/project-template/manifest.scm:6:1: error: packages->manifest: unbound variable
hint: Did you forget `(use-modules (guix profiles))'?

Like 9 April at 14:41 | Wall-to-wall | Open on mastouille.fr

4 comments

dave

@gugurumbe innnnteresting... it seems guix behaves differently depending on the flags used? 'guix shell -f manifest.scm' shows that error, but 'guix shell' doesn't! that's a very odd thing for guix to do, imo! I guess I should just explicitly include (guix profiles) to cover all the bases then. either hack your copy of the manifest as needed or just use plain ol 'guix shell' with no flags. and do see the README for the current caveats regarding the js-runtime directory.

9 April at 14:45 | Open on toot.cat

Vivien the Trumpeting Elephant

@dthompson Oh it’s because it should be called with -m manifest.scm, not -f manifest.scm. (without specifying manifest.scm, it does not want to run because security something)

9 April at 14:50 | Open on mastouille.fr

dave

@gugurumbe oh right! In my head I was thinking it was -m not -f! Totally missed that. Yeah Guix issues that security message when invoking its automatic behavior. If you do the echo command it prints out it will allow the next invocation to work.

9 April at 15:00 | Open on toot.cat

Vivien the Trumpeting Elephant

@dthompson Thanks, but I don’t want to change my home for each package that I’m trying. Otherwise it will be an indescriptible mess in a few years.

9 April at 15:22 | Open on mastouille.fr