unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: rendaw <7e9wc56emjakcm@s.rendaw.me>
To: amirouche@hyper.dev
Cc: Help-Guix <help-guix-bounces+amirouche=hyper.dev@gnu.org>,
	help-guix@gnu.org
Subject: Re: guile scheme tutorial
Date: Tue, 7 May 2019 11:15:26 +0900	[thread overview]
Message-ID: <baec03f0-c829-5daa-354c-6e549e4566b7@s.rendaw.me> (raw)
In-Reply-To: <007b2bd7409b29dadddc61c0c67d97ab@hyper.dev>


On 5/4/19 8:02 PM, amirouche@hyper.dev wrote:
> On 2019-05-04 08:08, rendaw wrote:
>> On 5/3/19 9:45 PM, amirouche@hyper.dev wrote:
>>> Hello!
>>>
>>>
>> (Whoops, replied with the wrong account.)
>>
>> Oh, this is great!  I've actually been putting together a small Guix
>> guide here:
>> https://gitlab.com/rendaw/blog/blob/master/how_to_guix_for_those_who_dont.md
>>
>>
>> It has a small Guile primer, but it doesn't go into depth or have any
>> hands on examples like yours.  My goal was to cover just enough so that
>> people could understand Guix configs (or at least 90% of them), so no
>> recursion, etc.  I'm glad you got into records, I just kind of handwaved
>> that away ("they're functions", not 100% sure this is correct either).
>
> That is good. The beginning looks like guix is not worthwhile and then
> you continue in the second page with an introduction to guile and guix.
> I find it nice actually.
>
> I spotted a minor error:
>
>   (system* (string-append #$openssl "/bin/openssl")
>            "genrsa" "-out" private-key "2048"))
>
>  
> https://gitlab.com/rendaw/blog/blob/master/how_to_guix_for_those_who_dont.md#running-executables
>
> Indeed you can run programs like that but in guix it is preferred to run
> with invoke, see the source :)
>
> Thanks for sharing!

Oh awesome, thanks!  I saw the recommendation to use invoke (in the
package guide?) but actually I'd like to know what the difference
between invoke and system* are... the code above was something I grabbed
from the Guix source somewhere (cups.scm?)

I just checked now (defined in guix/build/utils.scm) and it looks like
invoke raises an exception if the command has a non-zero exit, but
otherwise they're the same.

One more note for the guide I guess :D

  parent reply	other threads:[~2019-05-07  2:20 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
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 [this message]
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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=baec03f0-c829-5daa-354c-6e549e4566b7@s.rendaw.me \
    --to=7e9wc56emjakcm@s.rendaw.me \
    --cc=amirouche@hyper.dev \
    --cc=help-guix-bounces+amirouche=hyper.dev@gnu.org \
    --cc=help-guix@gnu.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).