From: Leo Famulari <leo@famulari.name>
To: Emmanuel Medernach <emmanuel.medernach@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Help on writing package definitions
Date: Thu, 23 Apr 2020 12:44:20 -0400 [thread overview]
Message-ID: <20200423164420.GA31443@jasmine.lan> (raw)
In-Reply-To: <CAC_pKx_L0H_ZLex8d1kM0qEsPrtomvKSTijp6bqGhpDSknGV7g@mail.gmail.com>
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.
next prev parent reply other threads:[~2020-04-23 16:55 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 [this message]
2020-04-23 17:11 ` zimoun
-- 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=20200423164420.GA31443@jasmine.lan \
--to=leo@famulari.name \
--cc=emmanuel.medernach@gmail.com \
--cc=help-guix@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.
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).