From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Ricardo Wurmus <rekado@elephly.net>, help-guix@gnu.org
Cc: rendaw <7e9wc56emjakcm@s.rendaw.me>
Subject: Re: Guix cookbook (was: guile scheme tutorial)
Date: Thu, 09 May 2019 17:14:59 +0200 [thread overview]
Message-ID: <87imujfymk.fsf@ambrevar.xyz> (raw)
In-Reply-To: <871s18elz8.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 516 bytes --]
I agree with all your points!
Regarding the bootstrapping process: we could already split the
packaging tutorial into 2 "recipes":
- A guile primer
- The actual packaging tutorial
Of course we would interlink them.
Once done, we should not forget to update the blog post to let the
readers know to refer to the corresponding cookbook instead.
Out of curiosity, can you remember which part of the tutorial is out of
date? I cannot think of anything.
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-05-09 15:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-03 12:45 guile scheme tutorial amirouche
2019-05-03 17:15 ` Guy fleury
2019-05-03 21:11 ` Laura Lazzati
2019-05-03 23:44 ` amirouche
2019-05-04 1:51 ` rendaw
2019-05-04 6:08 ` rendaw
2019-05-04 8:57 ` Ludovic Courtès
2019-05-07 4:35 ` rendaw
2019-05-08 12:46 ` Ludovic Courtès
2019-05-08 13:15 ` Pierre Neidhardt
2019-05-08 16:35 ` swedebugia
2019-05-13 7:10 ` rendaw
2019-05-13 8:00 ` Pierre Neidhardt
2019-05-08 20:21 ` Guix cookbook (was: guile scheme tutorial) Ricardo Wurmus
2019-05-09 15:14 ` Pierre Neidhardt [this message]
2019-05-09 21:38 ` Ricardo Wurmus
2019-05-13 9:08 ` Guix cookbook swedebugia
2019-05-04 11:02 ` guile scheme tutorial amirouche
2019-05-04 11:25 ` Laura Lazzati
2019-05-07 2:15 ` rendaw
2019-05-07 7:09 ` amirouche
2019-06-06 15:45 ` Laura Lazzati
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=87imujfymk.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=7e9wc56emjakcm@s.rendaw.me \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.net \
/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.