From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: bioinformatics.scm vs bioconductor.scm ?
Date: Tue, 18 Dec 2018 19:26:20 +0100 [thread overview]
Message-ID: <20181218192620.41ec9ad9@alma-ubu> (raw)
In-Reply-To: <CAJ3okZ3_4tzHHYO5aEOv=wh7qQnzb_6ZEHe_GvdBTbbpqi+v_A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 871 bytes --]
On Tue, 18 Dec 2018 06:31:44 -0500
zimoun <zimon.toutoune@gmail.com> wrote:
> What is the convention about license ?
> (license name) or (license license:name)
Just about this point: This is not a "convention", this is part of the
language definition of Guile, the underlying Scheme implementation:
In the module gnu/packes/cran.scm (and many others too) you find:
(define-module (gnu packages cran)
#:use-module ((guix licenses) #:prefix license:)
#:use-module (guix packages)
[...]
)
That means: use everything from module "guix licenses" and prefix it
with "license:". So, in the cran module, you must use "license:name" to
use the publicly defined "name" from the "guix licenses" module.
In other packages that import "guix licenses" without the prefix, you
use "name" directly. See gnu/packages/scsi.scm for an example.
Björn
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2018-12-18 18:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 18:21 bioinformatics.scm vs bioconductor.scm ? zimoun
2018-12-12 3:44 ` Ricardo Wurmus
2018-12-12 11:42 ` zimoun
2018-12-12 12:45 ` Ricardo Wurmus
2018-12-18 11:31 ` zimoun
2018-12-18 18:26 ` Björn Höfling [this message]
2018-12-18 18:36 ` zimoun
2018-12-18 22:49 ` Ricardo Wurmus
2018-12-18 22:45 ` Ricardo Wurmus
2018-12-20 8:46 ` Ricardo Wurmus
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=20181218192620.41ec9ad9@alma-ubu \
--to=bjoern.hoefling@bjoernhoefling.de \
--cc=guix-devel@gnu.org \
--cc=zimon.toutoune@gmail.com \
/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).