Notices

1. Jeko (jeko@framapiaf.org)'s status on Thursday, 21-Apr-2022 00:12:48 CEST Jeko

   in reply to

   • taiju :gnu: :emacs: :guix:

   @taiju
   I write a manifest everytime I start a project. It's the initial commit haha

   • Ekaitz Zárraga 👹 repeated this.
   • Robby (robby@zoinks.one)'s status on Thursday, 21-Apr-2022 00:12:48 CEST Robby

     in reply to

     • taiju :gnu: :emacs: :guix:
     @jeko @taiju Something I started doing is creating two files: my-package-name.scm and a manifest.scm. In the former I define the actual package object, so I could just `guix install/shell -f my-package-name.scm` to use the package. In the latter I just put `(package->development-manifest (load "my-package-name.scm"))` so I can run `guix shell` to get a development shell. This pattern works well for me :)
   • taiju :gnu: :emacs: :guix: (taiju@fosstodon.org)'s status on Thursday, 21-Apr-2022 00:12:54 CEST taiju :gnu: :emacs: :guix:

     I think I may have figured out the trick to building an environment when creating an application in Guile.

     By creating a `manifest.scm` in the project root and specifying Guile and the Guile libraries, I can use the `guix shell` to enter the development environment in which they are provided.

     If I use `guile --listen` to launch the REPL in that environment, I can use it from Emacs with the `geiser-connect` command.

     #guile #guix

   • Robby (robby@zoinks.one)'s status on Thursday, 21-Apr-2022 09:41:16 CEST Robby

     • Ekaitz Zárraga 👹

     @ekaitz_zarraga I’ve thought about that, it’s probably a good thing to do. I haven’t put too much effort into figuring that one out, since reproducibility isn’t a major need for me. I mostly just use guix for tracking my dependencies, and other conveniences that it provides. Do you just drop in the channenls file in the root of the project? Does that automatically get picked up?

     @taiju@fosstodon.org @jeko