On Friday, 21 August 2020 22:59:32 CEST Ekaitz Zarraga wrote:
> Thanks for bringing the question btw. I was worried about my workflow being
> correct and it happens to be!
Yeah, I wouldn't be surprised if there are more people who would like to
contribute, but then stumble on these minor
On Fri, Aug 21, 2020 at 10:51:29PM +0200, HiPhish wrote:
> OK, I'll try that. My main concern was with packages I actually want to run.
> For example, last time I wanted to update the Neovim version, so I changed
> the
> definition and installed Neovim in order to try it out a bit. But doing so
> I should have done `environment --ad-hoc`.
If it helps: that's exactly what I do.
Thanks for bringing the question btw. I was worried about my workflow being
correct and it happens to be!
On Tuesday, 18 August 2020 22:33:53 CEST Leo Famulari wrote:
> I recommend not using a different local state directory. There should
> not be any negative (or even observable) effects of your experimental
> artifacts being in /gnu/store. I haven't tried managing multiple stores
> but I assume
You might be interested in my video where I contribute a tiny patch to
the guix cookbook. I'm sure that my workflow could use some
improvement, but you might find some ideas here:
https://video.hardlimit.com/videos/watch/3c1df4c5-392a-44a9-b615-bab533a66231
--
Joshua Branson
Sent from Emacs
On Tue, Aug 18, 2020 at 08:38:39PM +0200, HiPhish wrote:
> My first question is regarding `guix git authenticate`. The first time I ran
> it
> after a `git clone ...` and `guix environment guix` I got an error saying
> that
> the `keyring` branch cannot be found. So I did a `git checkout
Hello everyone,
I am trying to get more serious about Guix, and I have a few questions about
how to develop Guix and the associated Git workflow. The manual in chapter 14.1
(Building from Git) explains most things pretty well.
My first question is regarding `guix git authenticate`. The first
