I am pleased to announce the availability of Planet
Guix , an Atom and RSS aggregator covering all
things Guix. You can browse posts on the website or use your favourite feed
reader to subscribe to the aggregate feed . Planet Guix already has subscriptions to 19 blogs from around the community;
if you write about Guix (no matter how infrequently) and would like your blog to
be included, or if you would like to suggest another blog I missed, please
create a pull request against the repository in
Codeberg — you'll see that the
subscriptions are simply configured as association…
Yesterday, I got access to a virtual machine from my university for
a school project. Great! The only catch: it was only accessible in
the internal network via an obscure VPN protocol.
We're on our way It's been a month since we started the fundraising campaign to Sustain and Strengthen Guix. So far we've raised €6562 which is around 40% of our €15000 annual goal. If you'd like to support the project's fundraiser there's still time, pop over to the donate page now! DONATE NOW There have been a range of donations, both one-off and recurring. A few people have made large one-off donations, one of over €2150!There have been a couple between €500-€250 and a…
Guile Load Path is a place (or more precisely places), where Guile
looks for the source code. This is the first thing one needs to set
correctly to work on a Guile Scheme project. It makes Guile aware
both of your own modules and external dependencies. For more details
refer to Load
Paths
page in Guile Reference Manual. This guide will focus on getting and
setting the right values for it and discussing different approaches to
do so.
A blog post documented an elegant way to configure screenshots in
wayland using grim and grimshot. After moving my sway config to use
the GUIXsway-service to generate the config file Iost my configured
screenshot bindings.
In our efforts to create a Tiny Build Farm for Guix, that is supposed
to report on the status of the packages assigned to the science team,
so far we have seen how to
set up
the required infrastructure.
On a dedicated machine with Guix as its operating system, we have added
several Shepherd services:
the Guix Build Coordinator together with a build agent;
and the web server part of the BFFE, which enables us to follow the
activity of the builders.
For performance reasons, we have renounced at installing an instance of the
Guix Data Service, and opt instead for talking to the instance operated
by the Guix project at https://data.guix.gnu.org/, which
continually evaluates the Guix master branch and creates derivations for
all packages in the distribution.
The next step is to explore how to programmatically talk to the remote
data server from a Guile script, how to extract derivations we are
interested in, and how to submit them for building to our instance of the
build coordinator.
This fictional story begins more than 10 years ago. I was a student at
technical university and was confused by how outdated some of the
programming-related courses are. I was checking out a few first
lections and usually skipping the rest of them (except a couple
courses that were fun and uptodate). In my spare time I was tinkering
on gentoo linux, cybersecurity and competitive programming
(codeforces, ACM ICPC, etc). I wanted to start working ASAP, so that I
could finally get to the most interesting part, but man, how wrong I
was...
About
Planet Guix is a meta-blog that collects posts from the blogs of various Guix hackers and contributors.