From: Mark H Weaver <mhw@netris.org>
To: Roel Janssen <roel@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: 01/01: gnu: Add perl-inline-c.
Date: Tue, 03 Apr 2018 15:34:50 -0400 [thread overview]
Message-ID: <87bmf0ccdh.fsf@netris.org> (raw)
In-Reply-To: <20180403170021.jmctpswhcfniblt3@abyayala> (Nils Gillmann's message of "Tue, 3 Apr 2018 17:00:21 +0000")
Nils Gillmann <ng0@n0.is> writes:
>> > Ludovic Courtès <ludo@gnu.org> writes:
>> >
>> >> 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?
I'm not a laywer, but if a future version of 'perl' were released under
a different license, I strongly doubt that this would retroactively
change the licenses of any earlier works. That's exactly what would
happen in Guix if we write (license (package-license perl)) and then
later change the 'license' field of the 'perl' package.
Mark
next prev parent reply other threads:[~2018-04-03 19:35 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 [this message]
2018-04-03 19:51 ` Nils Gillmann
2018-04-03 20:14 ` Mark H Weaver
2018-04-03 21:20 ` Ricardo Wurmus
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
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=87bmf0ccdh.fsf@netris.org \
--to=mhw@netris.org \
--cc=guix-devel@gnu.org \
--cc=roel@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).