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: Thu, 18 Mar 2021 07:33:04 +0100 [thread overview]
Message-ID: <d144260cff4e907bd263b4f4dbb1a3022ec94ef5.camel@zaclys.net> (raw)
In-Reply-To: <X0AJfvGmJvZOXkqcxiL1wDpQGbPYwaMG5V24ltJiXsvMhc8i8OZkWd_uAf18tMpgcSq1izVJTiurVFRaflG2_dOtTi7UzrOZwT9DcV0gFo0=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 2326 bytes --]
On Wed, 2021-03-17 at 03:42 +0000, ZmnSCPxj wrote:
> I understand.
>
> This will require a largish amount of work I think.
>
> Would this technique be acceptable?
>
> * `add-before 'configure 'unvendor-externals`
> * `rm -rf` the vendored externals.
> * `ln -s` the needed `.h` and `.la`/`.a`/`.so` files from the
> `inputs` to the expected paths within the `external/` directory.
>
> ?
Maybe simply add an option like --with-system-libbacktrace etc. in the
build system? And yes remove externals, I think that you should use a
snippet in the origin field instead of a phase for that.
>
> We have a `requirements.txt` file which contains this, I duplicate
> below:
>
> ```
> # Dependencies required to build and test c-lightning
> https://github.com/ElementsProject/libwally-core/releases/download/release_0.8.0/wallycore-0.8.0-cp36-cp36m-linux_x86_64.whl; 'linux' in sys_platform and python_version ==
> '3.6'
> https://github.com/ElementsProject/libwally-core/releases/download/release_0.8.0/wallycore-0.8.0-cp37-cp37m-linux_x86_64.whl; 'linux' in sys_platform and python_version ==
> '3.7'
> https://github.com/ElementsProject/libwally-core/releases/download/release_0.8.0/wallycore-0.8.0-cp37-cp37m-macosx_10_14_x86_64.whl; sys_platform == 'darwin' and python_version ==
> '3.7'
> mrkd ~= 0.1.6
> Mako ~= 1.1.3
>
> # Dependencies from pyln-client
> Sphinx ~= 3.4.0
> flake8==3.7.8
> recommonmark>=0.7.*
> sphinx-rtd-theme==0.4.2
> sphinxcontrib-websupport==1.1.0
> tqdm==4.32.2
>
> # Dependencies from pyln-testing
> Flask==1.1.*
> cheroot==8.5.*
> ephemeral-port-reserve==1.1.1
> filelock==3.0.*
> flaky ~= 3.7.0
> psutil==5.7.*
> psycopg2-binary==2.8.*
> pytest-rerunfailures==9.1.1
> pytest-timeout ~= 1.4.2
> pytest-xdist ~= 2.2.0
> pytest==6.1.*
> python-bitcoinlib==0.11.*
>
> # Dependencies from pyln-proto
> base58 ~= 2.0.1
> bitstring ~= 3.1.6
> coincurve ~= 13.0.0
> cryptography ~= 3.2
> mypy ~= 0.790
> pysocks ~= 1.7.1
>
> # Dependencies from pyln-spec
> # None
> ```
Thank you, I am going to go through them.
> Incidentally, we also install some Python modules.
> How do I "properly" export the Python modules within Guix?
I will ask someone else here but you might have to mix the python-
build-system in.
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-18 6:34 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
2021-03-17 3:42 ` ZmnSCPxj via Guix-patches via
2021-03-18 6:33 ` Léo Le Bouter via Guix-patches via [this message]
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
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=d144260cff4e907bd263b4f4dbb1a3022ec94ef5.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 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).