all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Dev@icepic" <dev@icepic.de>
To: Marius <mariusgr@disroot.org>, Marius via <help-guix@gnu.org>,
	Edouard Klein <edou@rdklein.fr>
Cc: help-guix@gnu.org
Subject: Re: Guix learning exercices
Date: Thu, 21 Nov 2024 20:41:55 +0100	[thread overview]
Message-ID: <C4ABB565-25FF-4858-B9FE-4CC101947F9E@icepic.de> (raw)
In-Reply-To: <AC02C166-3E22-4A6C-BE39-C41E208425D3@disroot.org>

Hey Marius!

I am Guix and scheme newbie myself. I can't provide you with concrete learning materials, just some tips from my journey.

I have learned a ton by working on a real project, namely, I try to port guix to a custom arm32 board using cross compilation. Cross compilation seems to be undersupported, so I stumbled upon multiple bugs, which I tried and partly succeeded to fix. Most of the time I spend reading the guix source code and try to understand what is going on. By doing so I learned a lot about how to write package definition, how to setup dev env using guix shell, how the mail driven development process works and much more. 

Have you considered a similiar approach for you? Maybe you are missing a package where you could provide a package definition. Or you look for a bug on the Issue tracker you could fix? For me getting my hands dirty and working towards a defined goal works best as learning process.

Best regards

Christoph

  reply	other threads:[~2024-11-21 19:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-21 17:11 Guix learning exercices Marius via
2024-11-21 17:55 ` Michael Dahlberg
2024-11-21 18:00 ` Josh Marshall
     [not found] ` <59D1033D-FCAF-4F51-8CD7-F6CC5FCAF578@rdklein.fr>
2024-11-21 18:20   ` Marius via
2024-11-21 19:41     ` Dev@icepic [this message]
     [not found] ` <pCiIhh1OYLyNDBMR5pyo_i94TmEM9rMMIl2szT_ODeGjlZBoqaX3bJ9IjeIPcjn70hY70oIv3HUflrOShQ0LoBSExoAtVtHy5t8vZjR4nXg=@recursoft.org>
2024-11-21 18:41   ` Marius via

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C4ABB565-25FF-4858-B9FE-4CC101947F9E@icepic.de \
    --to=dev@icepic.de \
    --cc=edou@rdklein.fr \
    --cc=help-guix@gnu.org \
    --cc=mariusgr@disroot.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.