unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: 宋文武 <iyzsong@envs.net>
Cc: 宋文武 <iyzsong@member.fsf.org>, 57133@debbugs.gnu.org
Subject: [bug#57133] [PATCH] gnu: Add rizin.
Date: Fri, 26 Aug 2022 15:49:48 +0200	[thread overview]
Message-ID: <f1f7d1da-fcdd-a0e9-8d7d-85c1ebc211fe@telenet.be> (raw)
In-Reply-To: <87wnbai92f.fsf_-_@envs.net>


[-- Attachment #1.1.1.1: Type: text/plain, Size: 845 bytes --]


On 15-08-2022 03:34, 宋文武 wrote:
>> You can put multiple licenses in the license field, using (license
>> (list this that foo bar ...)).
> For the license field, do we need to list all licenses of source code
> files, or the whole license of the package?  And if the later,
> `(list license:gpl2+ license:lgpl3+)` would say the package is dual
> licenses, under GPL2+ or LGPL3+ at user's choice.
>
> I think with all those licenses, the whole package is under
> GPL-3.0-or-later.
>
> Correct me if wrong, thank you!
I do not think it's stated anywhere which one exactly, but my own 
interpretation of the 'license' field is 'all the relevant licenses', 
without any claims whether it is a 'choose this or that' situation or a 
'one component is licensed as X, another is licensed as Y' situation.

Greetings,
Maxime.


[-- Attachment #1.1.1.2: Type: text/html, Size: 1336 bytes --]

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

  parent reply	other threads:[~2022-08-26 13:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-11  6:37 [bug#57133] [PATCH] gnu: Add rizin iyzsong--- via Guix-patches via
2022-08-11 12:44 ` Jean Pierre De Jesus DIAZ via Guix-patches via
2022-08-15  1:36   ` 宋文武 via Guix-patches via
2022-08-11 19:07 ` Maxime Devos
2022-08-15  1:34   ` 宋文武 via Guix-patches via
2022-08-19  1:20     ` bug#57133: " 宋文武 via Guix-patches via
2022-08-26 13:49     ` Maxime Devos [this message]
2022-08-26 13:54     ` [bug#57133] " Maxime Devos

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=f1f7d1da-fcdd-a0e9-8d7d-85c1ebc211fe@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=57133@debbugs.gnu.org \
    --cc=iyzsong@envs.net \
    --cc=iyzsong@member.fsf.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).