From: Arun Isaac <arunisaac@systemreboot.net>
To: guix-devel@gnu.org
Subject: Re: Etymology of derivation
Date: Mon, 02 Nov 2020 20:07:28 +0530 [thread overview]
Message-ID: <87sg9rlt93.fsf@systemreboot.net> (raw)
In-Reply-To: <CAF-xJgvjV2aJDEUUB9FxRACvLrwR+q9s9SSKeqnjQ=2RBRyNKg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 898 bytes --]
Thank you all for your inputs!
The original Nix publication was helpful. On page 22 of the full thesis,
it says:
--8<---------------cut here---------------start------------->8---
Derivation is Nix-speak for a component build action, which derives
the component from its inputs.
--8<---------------cut here---------------end--------------->8---
Direct loan words similar to "derivasyon" are possible. But, they would
be a last resort. வழித்தோன்றல் is surprisingly good, but I think I'll
construct a calque along the lines of "build-message". That seems to be
the most meaningful approach.
It's probably too much trouble now, but even in English, it would help
to have something more descriptive than "derivation". I remember
struggling with the term when first introduced to Guix. "build-message"
would have been much more self-descriptive.
Cheers!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 524 bytes --]
next prev parent reply other threads:[~2020-11-02 14:38 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sg9rlt93.fsf@systemreboot.net \
--to=arunisaac@systemreboot.net \
--cc=guix-devel@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 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.