unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: help-guix <help-guix@gnu.org>,
	Emmanuel Medernach <emmanuel.medernach@gmail.com>
Subject: Re: Help on writing package definitions
Date: Thu, 23 Apr 2020 19:11:56 +0200	[thread overview]
Message-ID: <CAJ3okZ1UUm4OHROvYXdyntZORmeb0uggLGKcwHYKo6mgXTkpFw@mail.gmail.com> (raw)
In-Reply-To: <20200423164420.GA31443@jasmine.lan>

On Thu, 23 Apr 2020 at 18:55, Leo Famulari <leo@famulari.name> wrote:
>
> On Thu, Apr 23, 2020 at 08:32:35AM +0200, Emmanuel Medernach wrote:
> > - Why not export the license record type from license.scm ? Some project
> > has its own license and I cannot create it.
>
> In general, we don't add project-specific licenses to licenses.scm or as
> their own variables.
>
> Instead, we use the non-copyleft, fsf-free, or fsdg-compatible license
> variables.

Considering the inclusion of such packages in Guix.

But if one wants to define its own custom license used by its own
custom package living in its own custom channel, then the API needs to
expose the 'license' record. Done here [1].

[1] http://issues.guix.gnu.org/40795


Cheers,
simon

  reply	other threads:[~2020-04-23 17:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-23  6:32 Help on writing package definitions Emmanuel Medernach
2020-04-23 10:00 ` zimoun
2020-04-23 12:21   ` Emmanuel Medernach
2020-04-23 14:17     ` zimoun
2020-04-23 16:44 ` Leo Famulari
2020-04-23 17:11   ` zimoun [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-04-23  9:41 Vincent Legoll
2020-04-23 12:09 ` Emmanuel Medernach
2020-04-23 12:17   ` Vincent Legoll

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=CAJ3okZ1UUm4OHROvYXdyntZORmeb0uggLGKcwHYKo6mgXTkpFw@mail.gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=emmanuel.medernach@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=leo@famulari.name \
    /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. 
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).