Re: Sockets in Shepherd, and Emacs, oh my!

2022-04-20 Thread Ludovic Courtès
Hi, Liliana Marie Prikler skribis: > Thinking about it some more, I am probably dumb and forgot #:respawn? > #t. Looking at my mail, it most definitely seems as though I did. > Well, that's a lesson learned, #:respawn? is #f normally. Oh right, you need #:respawn? #t if you want it to be resp

Re: Shepherd erroring on guix system reconfigure

2022-04-20 Thread Ludovic Courtès
Hi, Ludovic Courtès skribis: > "B. Wilson" skribis: > >> After pulling about an hour ago and attempting to reconfigure, it looks like >> shepherd is falling over, even though the reconfigure command finishes: >> >> activating system... >> The following derivation will be built: >>

Re: How to find binaries in libexec dir?

2022-04-20 Thread Allan Adair
Hi! I'm not sure if the following suggestion is a canonical way of doing things (I'm a scheme newb), but it is possible to define a package variant of diffoscope with a G-expression that uses wrap-program (see guix/build/utils.scm) to include paths to dependencies as part of an environment variabl

Re: 10 years of stories behind Guix

2022-04-20 Thread Rene Saavedra
Happy birthday Guix community :)

Haskell updates: GHC 9 and Stackage 19

2022-04-20 Thread Lars-Dominik Braun
Hi everyone, it’s time to update our Haskell environment – again. GHC 9.0 has been out for a while and Stackage updated its LTS distribution to version 19 recently, providing a new set of packages for GHC 9.0. Additionally there some issues/patches regarding haskell-build-system and the importer,

Viewing derivation output in the store

2022-04-20 Thread Brian Cully
I apologize if this isn’t the right place to ask these questions. While this is on the level of beginner tutorial (or should be, IMHO), the devel list seemed the most relevant. I’m trying to figure out how I can create a file and view it in the store before installation. I’d like

Re: Viewing derivation output in the store

2022-04-20 Thread Maxime Devos
Brian Cully schreef op wo 20-04-2022 om 11:40 [-0400]: > How do I go from the derivation in ’test-drv’ to the output in > the store? Something like how, from the REPL, this works: > > ---[snip]--- > scheme@(guile-user)> ,enter-store-monad > store-monad@(guile-user) [1]> (text-file "foo" "hel

Re: Updating from Go 1.17 to 1.18

2022-04-20 Thread Katherine Cox-Buday
>>> Pier-Hugues Pellerin writes: >> Ludovic Courtès writes: >>> I am trying to update Go to 1.18, I do have a *working* patch that defines >>> a package that inherits from 1.17 and that adjusts the inputs. >> >> Nice! Yes, thank you! I just found out I need this and came to see if anyone had sta

Re: Updating from Go 1.17 to 1.18

2022-04-20 Thread Pier-Hugues Pellerin
That sound great and great timing I was working on that as you send the mail I think also go-next is a good idea, I will split them in the following commits: 1. Add go-1.17 inherits from 1.18 (actually reversing the patch in the previous email) 2. Add go-next pointing to 1.18. 3. Make go point to

Re: Updating from Go 1.17 to 1.18

2022-04-20 Thread Pier-Hugues Pellerin
Hello, I've looked a bit more in detail on the Go package definition, Maybe we should rethink how we are building the Go package in guix? If I understand correctly, the current bootstrap chain is the following. 1.17 -> 1.16-> 1.4 which is the last gcc version of go. Looking at the current propos