From: ludo@gnu.org (Ludovic Courtès)
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: guix-devel <guix-devel@gnu.org>, guix-blog@gnu.org
Subject: Re: Blog: Guix packaging tutorial
Date: Sat, 29 Sep 2018 18:28:34 +0200 [thread overview]
Message-ID: <87wor4xo7h.fsf@gnu.org> (raw)
In-Reply-To: <87wor6269r.fsf@ambrevar.xyz> (Pierre Neidhardt's message of "Thu, 27 Sep 2018 19:34:56 +0200")
Hello!
Pierre Neidhardt <mail@ambrevar.xyz> skribis:
>> s/conventionally.*/typically used for read-only global variables/
>
> But aren't they generated in scope? I think we should mention this, or else
> new users try to access them out of scope.
I’m not sure what you mean by “generated in scope”.
The ‘%’ convention is just a convention (and Andy and I realized a while
back we interpreted the convention differently :-)) so we shouldn’t draw
too much from that.
Regarding ‘%build-inputs’ and ‘%outputs’, I think it’s enough to say
that these are global variables. Whether they are in scope depends on
whether a local variable shadows them.
Does that make sense?
>> It doesn’t make much sense to propagate a tarball, does it?
>
> Not really, but I just wanted to use "propagated input". We need a better
> example. Any idea?
The typical example are C, Python, or Guile libraries that propagate
libraries they depend on.
Another option is to skip propagated inputs altogether.
Thoughts?
>> > The astute reader may have noticed the quasi-quote and comma syntax in the
>> > argument field. Indeed, the build code in the package declaration should not be
>> > evaluated on the client side, but only when passed to the Guix daemon. This
>> > mechanism of passing code around two running processes is called [[https://arxiv.org/abs/1709.00833][code staging]].
>> > See [[https://www.gnu.org/software/guix/manual/en/html_node/G_002dExpressions.html][the "G-Expressions" chapter]] from the manual.
>>
>> Though precisely package definitions don’t use gexps yet… Not sure if
>> we should mention it; maybe it’s outside the scope of this tutorial.
>
> Hmmm... I think it's important to mention why code is not evaluated. Maybe this
> rather obscure paragraph could be simplified?
> I'll remove the mention to G-exp, it does not belong here indeed.
I think it’s good to mention code staging and the fact that there’s
“build-side code”, but the G-Expressions chapter says more than this,
which could be confusing.
>> > See https://guix.info/contact/ for the mailing lists, IRC, etc.
>>
>> For now please use gnu.org/software/guix URLs.
>
> Ok for this one, but I'd also like to link to the channels section in the
> manual, but it's not on gnu.org. Or is it?
Not yet. So yeah, you can use guix.info for this one if you need it.
> Last but not least, what should I do next? Should we wait for more reviews?
> Should I go ahead and push to master?
I suppose you can push to guix-artwork.git master; Ricardo? Please try
to use tags already used by the other articles.
When would you like it to be on line?
Thanks,
Ludo’.
next prev parent reply other threads:[~2018-09-29 16:28 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 10:50 Blog: Guix packaging tutorial Pierre Neidhardt
2018-09-13 11:16 ` Pjotr Prins
2018-09-13 11:53 ` Ricardo Wurmus
2018-09-13 12:04 ` Pjotr Prins
2018-09-13 19:11 ` Andreas Enge
2018-09-14 11:07 ` Pierre Neidhardt
2018-09-14 11:33 ` Pjotr Prins
2018-09-24 17:00 ` Pierre Neidhardt
2018-09-24 17:37 ` Pierre Neidhardt
2018-09-27 13:43 ` Ludovic Courtès
2018-09-27 17:34 ` Pierre Neidhardt
2018-09-29 16:28 ` Ludovic Courtès [this message]
2018-09-29 21:18 ` Ricardo Wurmus
2018-09-30 19:01 ` Pierre Neidhardt
2018-09-30 19:44 ` Ludovic Courtès
2018-09-30 21:14 ` Pierre Neidhardt
2018-10-02 12:12 ` Ludovic Courtès
2018-10-02 16:02 ` Pierre Neidhardt
2018-10-02 19:46 ` Ricardo Wurmus
2018-10-03 8:10 ` Pierre Neidhardt
2018-10-03 18:16 ` Pierre Neidhardt
2018-10-08 12:20 ` Ludovic Courtès
2018-10-08 15:18 ` Ricardo Wurmus
2018-10-08 18:41 ` Pierre Neidhardt
2018-10-08 19:06 ` Pierre Neidhardt
2018-10-08 19:59 ` Ricardo Wurmus
2018-10-08 22:09 ` Pierre Neidhardt
2018-10-08 22:33 ` Pierre Neidhardt
2018-10-08 23:45 ` Pierre Neidhardt
2018-10-10 11:56 ` Ludovic Courtès
2018-10-10 13:20 ` George Clemmer
2018-10-10 13:31 ` Pierre Neidhardt
2018-10-10 14:13 ` Ricardo Wurmus
2018-10-10 14:00 ` Guix packaging tutorial is on-line! Ludovic Courtès
2018-10-10 14:12 ` Pierre Neidhardt
2018-10-10 15:07 ` Ricardo Wurmus
2018-10-10 16:09 ` Pierre Neidhardt
2018-10-11 13:41 ` Ludovic Courtès
2018-10-11 16:34 ` Pierre Neidhardt
2018-10-11 16:51 ` Pierre Neidhardt
2018-10-15 12:02 ` Ludovic Courtès
2018-10-15 12:39 ` Pierre Neidhardt
2018-10-20 19:58 ` Blog: Guix packaging tutorial Divan
2018-10-21 10:30 ` Pierre Neidhardt
2018-10-21 11:21 ` Pierre Neidhardt
2018-10-22 20:40 ` Divan Santana
2018-10-22 21:11 ` Pierre Neidhardt
2018-09-26 10:20 ` Ludovic Courtès
2018-09-26 10:28 ` Pierre Neidhardt
2018-09-27 11:56 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2018-10-08 22:54 Benjamin Slade
2018-10-08 23:05 ` Pierre Neidhardt
2018-10-09 0:04 ` Benjamin Slade
2018-10-10 9:02 ` Ludovic Courtès
2018-10-11 1:38 ` Benjamin Slade
2018-10-11 9:37 ` Gábor Boskovits
2018-10-11 13:39 ` Ludovic Courtès
2018-10-12 1:05 ` Benjamin Slade
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=87wor4xo7h.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-blog@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mail@ambrevar.xyz \
/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.