From: Ricardo Wurmus <rekado@elephly.net>
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 23:49:20 +0100 [thread overview]
Message-ID: <87lg4mtpqn.fsf@elephly.net> (raw)
In-Reply-To: <CAJ3okZ0-bE-rxfGYAT03xrw3F+xJPMV7coUhMPk9YNzeBWDxWA@mail.gmail.com>
zimoun <zimon.toutoune@gmail.com> writes:
> Ok, but for example this convention about CRAN is not consistent with
> the importer. :-)
> guix import cran corpcor -r
> fills the license field with (license gpl3+) and not (license license:gpl3+)
That’s right. The importer does not know where the generated package
definition is supposed to be used.
> In other words, why the cran.scm needs a prefix for the license field?
It uses a prefix because we use the “zlib” package often, but not the
“zlib” license. We could exclude the “zlib” license from (guix
licenses), or import only a specified list of licenses, or we can solve
this naming conflict by prefixing all values from (guix licenses) with
“license:” (or anything else, really).
Really small modules often don’t have this problem in the first place,
so they don’t need to find a solution to work around the naming
conflicts.
--
Ricardo
next prev parent reply other threads:[~2018-12-18 22:49 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
2018-12-18 18:36 ` zimoun
2018-12-18 22:49 ` Ricardo Wurmus [this message]
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=87lg4mtpqn.fsf@elephly.net \
--to=rekado@elephly.net \
--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).