From: "Ludovic Courtès" <ludo@gnu.org>
To: muradm <mail@muradm.net>
Cc: 50217@debbugs.gnu.org
Subject: [bug#50217] [PATCH] gnu: Add c2ffi-11.0.0.
Date: Tue, 07 Sep 2021 16:06:18 +0200 [thread overview]
Message-ID: <87r1e04h0l.fsf_-_@gnu.org> (raw)
In-Reply-To: <20210827001207.4105-1-mail@muradm.net> (muradm's message of "Fri, 27 Aug 2021 03:12:07 +0300")
Hello,
muradm <mail@muradm.net> skribis:
> * gnu/packages/cpp.scm (c2ffi): New variable.
Overall LGTM, modulo the following minor issues:
[...]
> +(define-public c2ffi
> + (let ((commit "f50243926a0afb589de1078a073ac08910599582")
> + (revision "1")
> + (c2ffi-sha256 "17j73yb6v3lfvwwicl2f3yg141iz2dk1rf874qzqs5bkq64ldjsj"))
Normally, we only provide upstream releases. If you think we need this
specific commit, could you add a comment explaining why?
Please leave the base32 sha256 string where it’s used, within the
(base32 …) expression (it’s a macro that decodes base32 at
compile-time.)
> + #:tests? #f))
It would be best to run tests. Alternatively, if this is not feasible,
please add a comment explaining why we’re skipping them.
> + (synopsis "Clang-based FFI wrapper generator")
> + (description "tool for extracting definitions from C, C++, and
> +Objective C headers for use with foreign function call interfaces.")
Please write full sentences, as per
<https://guix.gnu.org/manual/en/html_node/Synopses-and-Descriptions.html>.
> + (license license:gpl2))))
Is it GPLv2-only? Unless it’s explicitly stated, it’s probably
GPLv2-or-later (‘license:gpl2+’).
Could you send an updated patch?
Thanks!
Ludo’.
next prev parent reply other threads:[~2021-09-07 14:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-26 21:07 [bug#50217] [PATCH] gnu: Add c2ffi-11.0.0 muradm
2021-08-27 0:12 ` [bug#50217] [PATCH v2] " muradm
2021-09-07 14:06 ` Ludovic Courtès [this message]
2021-10-25 15:14 ` [bug#50217] [PATCH v2] gnu: Add c2ffi Attila Lendvai
2022-01-12 17:13 ` [bug#50217] [PATCH v3] " Attila Lendvai
2022-02-14 12:31 ` [bug#50217] [PATCH v4] " Attila Lendvai
2022-02-14 15:30 ` Maxime Devos
2022-02-14 15:34 ` Maxime Devos
2022-02-14 15:41 ` Maxime Devos
2022-02-15 18:43 ` [bug#50217] [PATCH v5] " Attila Lendvai
2022-02-15 19:51 ` [bug#50217] [PATCH v6] " Attila Lendvai
2022-03-01 9:17 ` [bug#50217] [PATCH v7] " Attila Lendvai
2022-03-01 9:21 ` [bug#50217] [PATCH v8] " Attila Lendvai
2022-03-03 18:36 ` [bug#50217] [PATCH v9] " Attila Lendvai
2022-03-03 20:34 ` bug#50217: " Guillaume Le Vaillant
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=87r1e04h0l.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=50217@debbugs.gnu.org \
--cc=mail@muradm.net \
/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).