From: "Léo Le Bouter via Guix-patches via" <guix-patches@gnu.org>
To: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Cc: "47187@debbugs.gnu.org" <47187@debbugs.gnu.org>
Subject: [bug#47187] [PATCH] gnu: Add c-lightning.
Date: Tue, 16 Mar 2021 13:46:22 +0100 [thread overview]
Message-ID: <8f7d4c04d96fdf8cf1239c476c4c869f92446ada.camel@zaclys.net> (raw)
In-Reply-To: <Pnk0YahvVi3QLAGeLyIGEl3tdFaE1AtAtHOvIRjW1gPAUzzjYF9dC0U8Di_kRe84FfmQw_1hr7sSRE4enMKw0Kzd74mMvR-CGQyhWhZJelw=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 2820 bytes --]
On Tue, 2021-03-16 at 11:27 +0000, ZmnSCPxj wrote:
> Already working on that, but 0.10.0 will release soon and I doubt my
> changes will make it by then, so Guix might get c-lightning to 0.10.1
> or later if we wait for it.
Awesome!
> Yes, it is true that there is something of a requirement of a strict
> behavior here, I suppose it is possible to use `git-fetch` instead of
> `url-fetch` for our external libraries.
Yes you can use git-fetch, to make sure we are on the same page, are
you speaking of strict behavior requirements like for Bitcoin Core's
consensus code?
> How do I generate `guix hash` for `git-fetch`ed `source`s?
Actually what I do is put a wrong hash in and then copy the "actual
hash" from the error. I havent found another way but this definitely
feels subpar and prevents much verification before putting in the hash,
better suggestions welcome.
> However it also means that every release of C-Lightning I have to go
> double-check what git commit to use for each library (though `jsmn`
> and `libbacktrace` at least seem very stable).
>
> But it looks to me that unvendoring will require more extensive
> patching of the `Makefile` and an even larger maintenance burden on
> Guix side?
Unvendoring is more or less a policy because we must be able to audit
each piece of software separately for freedom issues (licenses,
violations to the GNU FSDG), and it eases work for security-patching
also.
> `libwally-core` itself depends on another library `libsecp256k1`, so
> I suppose it must transitively be unvendored as well.
Probably, we already have a libsecp256k1 specially for Bitcoin Core.
> The test suite is fairly large and can take a significant amount of
> time to run in full.
That's fine.
> In addition, part of the test includes checks which take advantage of
> `BINTOPKGLIBEXECDIR` relative path we normally use, which I want to
> disable for Guix at least since the relative path only has an
> advantage if the user wants to move the installation after-the-fact
> to a different location (and on Guix the "installation" path cannot
> be moved anyway).
> Using an absolute `BINTOPKGLIBEXECDIR` gives an advantage as
> mentioned in the comments that a profile being upgraded from one
> version of C-Lightning to another does not cause problems for daemons
> currently running off the profile.
> The test can be disabled (but not easily), I suppose.
Problematic or unrealistically expensive tests can be disabled yes.
> Please do, I am not very familiar with any Python infrastructure and
> am primarily a C programmer here, I just barely hack together some
> kind of test in Python.
If you can list the Python dependencies and their version I can look at
packaging them.
> Regards,
> ZmnSCPxj
Léo
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-03-16 12:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 8:40 [bug#47187] [PATCH] gnu: Add c-lightning ZmnSCPxj via Guix-patches via
2021-03-16 9:13 ` Léo Le Bouter via Guix-patches via
2021-03-16 9:17 ` Léo Le Bouter via Guix-patches via
2021-03-16 11:27 ` ZmnSCPxj via Guix-patches via
2021-03-16 12:46 ` Léo Le Bouter via Guix-patches via [this message]
2021-03-17 3:42 ` ZmnSCPxj via Guix-patches via
2021-03-18 6:33 ` Léo Le Bouter via Guix-patches via
2021-03-18 16:54 ` ZmnSCPxj via Guix-patches via
2021-03-19 9:09 ` Léo Le Bouter via Guix-patches via
2021-03-19 19:31 ` ZmnSCPxj via Guix-patches via
2021-03-21 21:42 ` Léo Le Bouter via Guix-patches via
2021-03-26 18:13 ` Léo Le Bouter via Guix-patches via
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8f7d4c04d96fdf8cf1239c476c4c869f92446ada.camel@zaclys.net \
--to=guix-patches@gnu.org \
--cc=47187@debbugs.gnu.org \
--cc=ZmnSCPxj@protonmail.com \
--cc=lle-bout@zaclys.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.