unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org, Nils Gillmann <ng0@n0.is>
Subject: Re: 01/01: gnu: Add perl-inline-c.
Date: Wed, 04 Apr 2018 10:37:05 +0200	[thread overview]
Message-ID: <876057gyfi.fsf@gnu.org> (raw)
In-Reply-To: <87sh8cj8c9.fsf@elephly.net> (Ricardo Wurmus's message of "Tue, 03 Apr 2018 23:20:06 +0200")

Ricardo Wurmus <rekado@elephly.net> skribis:

> Nils Gillmann <ng0@n0.is> writes:

[...]

>> 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.

Exactly.  The problem arose when we started writing (package-license
perl) in modules other than perl.scm but that were in a cycle with
perl.scm.

Ludo’.

      reply	other threads:[~2018-04-04  8:37 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
2018-04-04  8:37             ` Ludovic Courtès [this message]

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=876057gyfi.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=ng0@n0.is \
    --cc=rekado@elephly.net \
    /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).