Notices by Ludovic Courtès (civodul@toot.aquilenet.fr), page 2

Demain @zimoun parlera au ☕ Café de #Guix comme « usine à conteneurs et machines virtuelles ».

📆 mardi 28 janvier, 13h–14h
⯈ https://hpc.guix.info/events/2024-2025/caf%C3%A9-guix/

#RechercheReproductible

@nobody ‘run.cc’ has that chroot-helper thing with ‘unshare’ calls. :-)

@futurile I would love to reach out to the beginner/explorer type, for good.

After all, that’s the whole point of the “practical user freedom” stance, which led to the overall design and even to the way some of the documentation is written.

Probably we need more in the way of popular education?

@gugurumbe I wouldn’t say the survey presented lack of non-free software as a problem, but it’s true that it explicitly listed it as an option, particularly for drivers.

I’m not a maintainer but I don’t expect nor desire a change in what Guix provides: it should all be free software, and it’s fine to have third-party channels providing non-free software.

The question of non-free firmware could be discussed separately though, like it was in Debian.

On this topic, while I was looking for something else :-) I found that Lix (and Nix?) has what they call “installables”, which ‘nix run’ runs in a container:
https://git.lix.systems/lix-project/lix/src/branch/main/lix/nix/run.md

‘nix run’ seems to have the same goal as the wrapper produced by ‘guix pack -R’: mapping the store at the right place in the application’s namespace. It’s not about running an application with the least authority.

@kris I suppose some of the interface that’s currently private could move to (guix least-authority) for example. It’s just that providing a clean Scheme-level interface requires more thought.

@janneke QubesOS goes way beyond that, but in a way it’s a step in that direction, sure!

@fnat Sort of, yes. With ‘guix shell’ you end up with long command lines that you have to figure out by yourself (passing the right ‘--share’ and ‘-E’ flags, etc.).

Here ‘guix container run’ can guess based on the dependencies of what you want to run.

‘guix container run’ for least-authority program execution:
https://issues.guix.gnu.org/75595

Yay? Meh?

#Guix

Playing with the idea of "different perspectives on the same story"!

A QR code that sends you to a different source based on the angle.

The #Guix Consensus Document (GCD) process is open for deliberation to all team members until Feb. 5th 👇
https://issues.guix.gnu.org/74736#91

Exciting times!

@janneke @JeroenBaten Interesting! Sounds similar to Stow, which was from about the same period no? Or to “environment modules” (still widely used in HPC), which dates back to the mid-1990s.

@JeroenBaten What’s cadappl?

Meet #Guix at #FOSDEM!
https://guix.gnu.org/en/blog/2025/meet-guix-at-fosdem-2025/

En route pour le CINES. 🖧💪

@zimoun With teams and ‘CODEOWNERS’, you get notified only for things relevant to you.

And then, we have to admit that the messaging interface for issues/PRs rich, with automatic connections among them and with commits.

There’s also a search function for issues, available via ‘fj-list-issues-search’ (or ‘s’ from the issue list).

@Cuicas Gnus (with scoring and all the bells and whistles) and server-side filtering (Sieve).

As I use ‘M-x fj-view-notifications’, I start dreaming of a time where I’d no longer miss comments on patch reviews and at the same time regain control of my mailbox.

OK, I’m probably overly optimistic. Still…

There’s a patch adding a Hetzner backend to ‘guix deploy’:
https://issues.guix.gnu.org/75144

I think that’s pretty cool.

#Guix

@crowdagger Mais donc oui, peut-être « pensé » ?

@VioB