unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Arun Isaac <arunisaac@systemreboot.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Etymology of derivation
Date: Tue, 03 Nov 2020 20:13:54 +0530	[thread overview]
Message-ID: <875z6mlcut.fsf@systemreboot.net> (raw)
In-Reply-To: <87blgeeesw.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 778 bytes --]


> Lower-level APIs are available to interact with the daemon and the
> store.  To instruct the daemon to perform a build action, users
> actually provide it with a “derivation”.  A derivation is a low-level
> representation of the build actions to be taken, and the environment
> in which they should occur—derivations are to package definitions what
> assembly is to C programs.  The term “derivation” comes from the fact
> that build results _derive_ from them.

This paragraph explains well what derivations are. But, it only helps a
bit with the rather confusing etymology of the word. "derive" and
"derivation" raise very familiar mathematical notions in our mind, that
it may not be possible to really explain our use of "derivation" very
easily.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 524 bytes --]

  reply	other threads:[~2020-11-03 15:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-01 19:27 Etymology of derivation Arun Isaac
2020-11-01 19:49 ` Vagrant Cascadian
2020-11-02  5:07 ` Taylan Kammer
2020-11-02  7:48   ` Aniket Patil
2020-11-02 14:37     ` Arun Isaac
2020-11-02 15:43       ` Pierre Neidhardt
2020-11-02 16:19         ` Pjotr Prins
2020-11-02 19:19           ` Arun Isaac
2020-11-03 13:43       ` Ludovic Courtès
2020-11-03 14:43         ` Arun Isaac [this message]
2020-11-03 14:53         ` Timothy Sample
2020-11-04  7:50           ` Arun Isaac
2020-11-04 10:17 ` zimoun

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=875z6mlcut.fsf@systemreboot.net \
    --to=arunisaac@systemreboot.net \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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.
Code repositories for project(s) associated with this public inbox

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

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).