On Mon, Jan 15, 2024 at 11:24:29AM -0800, Ian Eure wrote:
> Greetings,
>
> As I’ve been learning Guix, one of the things I’ve found somewhat unpleasant
> is the lack of consistency within the guix CLI tool. It feels a bit
> Git-like, with not much consistency, commands that non-obvioulsy perform
>
> Just my 2 cents, I imagine every person here has their own workflow.
I personally don't have any yet (and I assume I'm not the only one) so
I'm really thankful for your snippet.
Cheers Bost
Hi all,
When running guix deploy with a list of machines, the command will fail
if any of the machines are unreachable. I use Guix deploy from a central
machine to update the devices on my LAN, including laptops, which aren't
guaranteed to be on. I'm also not terribly worried about keeping eve
Hello,
This is very exciting work, thanks everyone!
"Antoine R. Dumont (@ardumont)" writes:
> FWIW, in the "new" lister [1] implementation, there are a bunch of extra
> computations done [1] to try and resolve those situations. It's trying
> to fetch more information from upstream server (e.g.
Hi all,
We're planning to put up a blog post about Guix (and Guix-related) talks
at FOSDEM [0]. I've collected all the talks that that are about Guix (or
connected areas). If I've missed any Guix related talks please tell me
so I can add them to the blog post:
- Declarative and Minimalist Co
On 2024-01-14 22:12:38 +0100, Troy Figiel wrote:
> Hi everyone,
>
> When looking into the Go build system, I noticed the default check phase
> runs (invoke "go" "test" import-path), which only runs the tests in the
> root directory of the source. Running the tests in all subdirectories
> would req
