From: Vagrant Cascadian <vagrant@debian.org>
To: Arun Isaac <arunisaac@systemreboot.net>, guix-devel@gnu.org
Subject: Re: Etymology of derivation
Date: Sun, 01 Nov 2020 11:49:00 -0800 [thread overview]
Message-ID: <87eelcoo2b.fsf@yucca> (raw)
In-Reply-To: <87v9eolvwy.fsf@systemreboot.net>
[-- Attachment #1: Type: text/plain, Size: 1495 bytes --]
On 2020-11-02, Arun Isaac wrote:
> I am translating Guix to the Tamil language. Tamil doesn't yet have a
> very standardized technical vocabulary, and I mostly coin terms on my
> own. Most often, I construct calques of existing English words, and it
> sounds alright. But, I'm having trouble with the word "derivation" (as
> in Guix's low-level build actions). I haven't seen the word "derivation"
> used anywhere outside of Guix. Why is a "low-level build action" called
> a "derivation"? If someone could clarify the etymology, it might really
> help with good translation.
From WordNet (r) 3.0 (2006) [wn]:
derivation
n 1: the source or origin from which something derives (i.e.
comes or issues); "he prefers shoes of Italian derivation";
"music of Turkish derivation"
...
8: the act of deriving something or obtaining something from a
source or origin
Seems like a some subtle variation of definitions 1 and 8, according to
wordnet. Closer to 8, really, so I'd say ...
The guix derivations are the result of processing or using (the act)
inputs (sources and origins) to produce an output (the derivation
itself).
I would guess the original Nix publication also explains the use of this
term?
https://web.archive.org/web/20190421081837/https://nixos.org/~eelco/pubs/iscsd-scm11-final.pdf
https://web.archive.org/web/20190609111633/https://nixos.org/~eelco/pubs/phd-thesis.pdf
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2020-11-01 19:49 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 [this message]
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
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=87eelcoo2b.fsf@yucca \
--to=vagrant@debian.org \
--cc=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 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).