unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: Martin Becze <mjbecze@riseup.net>
Cc: 44433@debbugs.gnu.org
Subject: [bug#44433] [PATCH 0/3] gnu: Add solidity.
Date: Mon, 16 Nov 2020 22:56:58 +0000	[thread overview]
Message-ID: <873618nc5h.fsf@cbaines.net> (raw)
In-Reply-To: <20201104122928.30408-1-mjbecze@riseup.net>

[-- Attachment #1: Type: text/plain, Size: 1335 bytes --]


Martin Becze <mjbecze@riseup.net> writes:

> This adds the Solidity compiler. It also updates Z3 and jsoncpp to versions
> needed by Solidity. I tested rebuilding quite a few packages that jsoncpp is a
> dependent of but I am not sure how to tests them all.
>
> Martin Becze (3):
>   gnu: jsoncpp: Update to 1.9.4
>   gnu: z3: Update to 4.8.9.
>   gnu: Add solidity.
>
>  gnu/local.mk                                  |  2 +-
>  gnu/packages/maths.scm                        |  5 +-
>  .../patches/jsoncpp-fix-inverted-case.patch   | 22 -----
>  gnu/packages/serialization.scm                |  6 +-
>  gnu/packages/solidity.scm                     | 88 +++++++++++++++++++
>  5 files changed, 95 insertions(+), 28 deletions(-)
>  delete mode 100644 gnu/packages/patches/jsoncpp-fix-inverted-case.patch
>  create mode 100644 gnu/packages/solidity.scm

Hi Martin,

Thanks for the patches, they look good. I've pushed the z3 update to
master, as that didn't have many dependent packages.

As you've noticed, jsoncpp has quite a few dependencies. The current
process to handle changes like this is to push them to the core-updates
branch. I have tried building jsoncpp on core-updates, but I'm having
problems with git, curl and HTTPS support...

I'll hopefully have some more time to investigate further in a bit,

Thanks again,

Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]

  parent reply	other threads:[~2020-11-16 22:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-04 12:29 [bug#44433] [PATCH 0/3] gnu: Add solidity Martin Becze
2020-11-04 12:29 ` [bug#44432] [PATCH 1/3] gnu: jsoncpp: Update to 1.9.4 Martin Becze
2020-11-05 14:04   ` bug#44432: close Martin Becze
2020-11-04 12:29 ` [bug#44431] [PATCH 2/3] gnu: z3: Update to 4.8.9 Martin Becze
2020-11-05 14:05   ` bug#44431: close Martin Becze
2020-11-04 12:29 ` [bug#44434] [PATCH 3/3] gnu: Add solidity Martin Becze
2020-11-05 14:03   ` bug#44434: closing Martin Becze
2020-11-05 13:59 ` [bug#44433] [PATCH 1/3] gnu: jsoncpp: Update to 1.9.4 Martin Becze
2020-11-05 13:59   ` [bug#44433] [PATCH 2/3] gnu: z3: Update to 4.8.9 Martin Becze
2020-11-05 13:59   ` [bug#44433] [PATCH 3/3] gnu: Add solidity Martin Becze
2020-11-18  8:22     ` Christopher Baines
2020-11-16 22:56 ` Christopher Baines [this message]
2020-11-18  8:17   ` bug#44433: [PATCH 0/3] " Christopher Baines

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=873618nc5h.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=44433@debbugs.gnu.org \
    --cc=mjbecze@riseup.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).