From: nils@promisedlandt.de
To: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Specifying licenses that are not included with guix
Date: Sat, 13 May 2023 11:36:39 +0200 (CEST) [thread overview]
Message-ID: <216678161.328421.1683970599623@office.mailbox.org> (raw)
Hello,
I'm currently packaging vim plugins. This is mostly going well, but I've hit some license-related issues.
1. What do I do if a package specifies a license that is not included in guix/licenses.scm ? For example, vim-sandwich uses the NYSL license [1] (between public-domain and WTFPL), coc.nvim is the originator of the "Anti 996" License [2] (modified version of MIT / expat).
2. What do I do if a package specifies no license at all? For example see https://github.com/coderifous/textobj-word-column.vim/issues/11
[1] https://github.com/machakann/vim-sandwich/blob/c5a2cc438ce6ea2005c556dc833732aa53cae21a/doc/sandwich.txt#L6-L8
[2] https://github.com/neoclide/coc.nvim/blob/3014125e4ab7d35e08bbcde946dca4812b84f105/LICENSE.md
next reply other threads:[~2023-05-13 9:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-13 9:36 nils [this message]
2023-05-15 12:05 ` Specifying licenses that are not included with guix Simon Tournier
2023-05-15 17:15 ` nils
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=216678161.328421.1683970599623@office.mailbox.org \
--to=nils@promisedlandt.de \
--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).