unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: iyzsong@envs.net, 57133@debbugs.gnu.org
Cc: 宋文武 <iyzsong@member.fsf.org>
Subject: [bug#57133] [PATCH] gnu: Add rizin.
Date: Thu, 11 Aug 2022 21:07:18 +0200	[thread overview]
Message-ID: <13b3d37d-f4c6-4850-900c-49b5cce8d4a8@telenet.be> (raw)
In-Reply-To: <20220811063749.8293-1-iyzsong@envs.net>


[-- Attachment #1.1.1: Type: text/plain, Size: 1560 bytes --]


On 11-08-2022 08:37, iyzsong--- via Guix-patches via wrote:
> +               #$(origin
> +                   (method git-fetch)
> +                   (uri (git-reference
> +                         (url"https://github.com/rizinorg/rizin-testbins")
> +                         (commit "7d0c31ac7711de9c4d37f5047200dc5a407ff713")))
> +                   (sha256
> +                    (base32
> +                     "00cmc7pws9m4hcm0bpdjm6n4agl5mqgczc4ccswfhywyzzvr7sqh")))
> +               "test/bins")))

What's the license for those binaries? I doubt all of them are gpl3+.

I'm seeing a copy of libstdc++.so.6 in there. IIRC, it has a license of 
the GPL family, which requires providing the source, so we need the 
source code of it as well because of the licensing terms (the source 
code of that particular variant of libstdc++, which might differ from 
the version currently in Guix). Likewise for the other binaries.

Personally, I think it would be more practical to ignore rizin-testbins, 
even if that requires skipping some of the tests (hopefully not all of 
them).
> + ;; Most files are under LGPL-3.0-only, other are under: Apache-2.0,
> + ;; BSD-2-Clause, BSD-3-Clause, CC0-1.0, CC-BY-SA-4.0, GPL-1.0-or-later,
> + ;; GPL-2.0-only, GPL-2.0-or-later, GPL-3.0-or-later, LGPL-2.0-or-later,
> + ;; LGPL-2.1-only, LGPL-2.1-or-later, LGPL-3.0-only, MIT, NCSA.
> + (license license:gpl3+))) 

You can put multiple licenses in the license field, using (license (list 
this that foo bar ...)).

Greetings,
Maxime.


[-- 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-11 19:08 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 [this message]
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     ` [bug#57133] " Maxime Devos
2022-08-26 13:54     ` 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=13b3d37d-f4c6-4850-900c-49b5cce8d4a8@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).