From: Ricardo Wurmus <rekado@elephly.net>
To: 60201-done@debbugs.gnu.org
Subject: bug#60201: [PATCH] gnu: Add libswell
Date: Wed, 04 Jan 2023 11:23:07 +0100 [thread overview]
Message-ID: <87bkne4mtm.fsf@elephly.net> (raw)
In-Reply-To: <ChXlp6YIa5eQPVrAFeG2FC6o26Dc5gy7wqxPRhNRHBYQbA9_bSFj5eVJ54SNCY-PGGkKddEU6il-w16cEoGvT2mV_B3pyxlGo6yMrwzy0H8=@proton.me>
Thank you for your patience.
I took the liberty of making a few changes:
- minor indentation / formatting changes
- pulled out the “with-directory-excursion” to simplify the snippet
- used “with-directory-excursion” where possible to avoid stateful
behavior across build phases.
- removed the “mkdir-p” which would have only created empty directories
in $out/include, and simplified installation of all headers.
- added a copyright line for you
It’s all pushed to the “master” branch with commit
a8f15711508abab85cba3174f68a4343a15fb116.
Thanks!
--
Ricardo
prev parent reply other threads:[~2023-01-04 10:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 13:49 [bug#60201] [PATCH] gnu: Add libswell Sughosha via Guix-patches via
2022-12-19 14:04 ` [bug#60201] [PATCH v2] gnu: libswell: align properly Sughosha via Guix-patches via
2022-12-19 18:16 ` [bug#60201] [PATCH v3] gnu/packages/wdl.scm: Remove unused module Sughosha via Guix-patches via
2022-12-22 18:08 ` [bug#60201] [PATCH v4] gnu: libswell: Modify inputs Sughosha via Guix-patches via
2022-12-22 19:08 ` [bug#60201] [PATCH v5] gnu: libswell: Lint and fix mistakes Sughosha via Guix-patches via
2022-12-30 17:33 ` [bug#60201] [PATCH v6] gnu/local.mk: Register wdl.scm Sughosha via Guix-patches via
2022-12-30 18:16 ` [bug#60201] [PATCH v7] gnu: Add libswell Sughosha via Guix-patches via
2023-01-02 11:32 ` [bug#60201] [PATCH] " Ricardo Wurmus
2023-01-03 22:09 ` [bug#60201] [PATCH v8] gnu: Add wdl Sughosha via Guix-patches via
2023-01-03 23:15 ` [bug#60201] [PATCH v9] " Sughosha via Guix-patches via
2023-01-04 10:23 ` Ricardo Wurmus [this message]
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=87bkne4mtm.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=60201-done@debbugs.gnu.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 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.