From: Ricardo Wurmus <rekado@elephly.net>
To: Nils Gillmann <ng0@n0.is>
Cc: guix-devel@gnu.org
Subject: Re: 01/01: gnu: Add perl-inline-c.
Date: Tue, 03 Apr 2018 23:20:06 +0200 [thread overview]
Message-ID: <87sh8cj8c9.fsf@elephly.net> (raw)
In-Reply-To: <20180403170021.jmctpswhcfniblt3@abyayala>
Nils Gillmann <ng0@n0.is> writes:
> Roel Janssen transcribed 509 bytes:
>>
>> Roel Janssen <roel@gnu.org> writes:
>>
>> > Ludovic Courtès <ludo@gnu.org> writes:
>> >
>> >> Hi Roel,
>> >>
>> >> roel@gnu.org (Roel Janssen) skribis:
>> >>
>> >>> + (license (package-license perl))))
>> >>
>> >> Could you use (license perl-license) instead? It doesn’t make any
>> >> difference in this case but it’s generally “safer” (see (guix
>> >> licenses)).
>
> Can you tell me why it is safer to say perl-license instead of package-license perl?
Following Ludo’s reference to “(guix licenses)” we can see this comment:
;; The license of Perl, GPLv1+ or Artistic (we ignore the latter here).
;; We define this alias to avoid circular dependencies introduced by the use
;; of the '(package-license perl)' idiom.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2018-04-03 21:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180403124356.20162.76789@vcs0.savannah.gnu.org>
[not found] ` <20180403124357.2ECCC204DA@vcs0.savannah.gnu.org>
2018-04-03 13:18 ` 01/01: gnu: Add perl-inline-c Ludovic Courtès
2018-04-03 13:27 ` Roel Janssen
2018-04-03 13:29 ` Roel Janssen
2018-04-03 17:00 ` Nils Gillmann
2018-04-03 19:34 ` Mark H Weaver
2018-04-03 19:51 ` Nils Gillmann
2018-04-03 20:14 ` Mark H Weaver
2018-04-03 21:20 ` Ricardo Wurmus [this message]
2018-04-04 8:37 ` Ludovic Courtès
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=87sh8cj8c9.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=ng0@n0.is \
/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.