From: "Ludovic Courtès" <ludo@gnu.org>
To: raingloom <raingloom@riseup.net>
Cc: 43976@debbugs.gnu.org
Subject: [bug#43976] [PATCH] Chicken build system + some example eggs
Date: Fri, 27 Nov 2020 10:09:29 +0100 [thread overview]
Message-ID: <87eekfxj1y.fsf@gnu.org> (raw)
In-Reply-To: <20201124212254.0c69b459@riseup.net> (raingloom@riseup.net's message of "Tue, 24 Nov 2020 21:22:54 +0100")
Hi raingloom!
raingloom <raingloom@riseup.net> skribis:
> From 2ba52705cf909590a428ea598dfdf1c61ada6a8c Mon Sep 17 00:00:00 2001
> From: raingloom <raingloom@riseup.net>
> Date: Mon, 12 Oct 2020 04:11:59 +0200
> Subject: [PATCH 01/20] gnu: Added search paths for Chicken Scheme.
>
> * gnu/packages/chicken.scm (chicken): Added search paths
> [native-search-paths]: added CHICKEN_REPOSITORY_PATH and a comment about
> CHICKEN_INCLUDE_PATH.
[...]
> + (native-search-paths
> + (list (search-path-specification
> + (variable "CHICKEN_REPOSITORY_PATH")
> + ;; TODO extract binary version into a module level definition.
> + (files (list "var/lib/chicken/11")))))
> + ;; the use of this variable is unclear. the online docs don't even
> + ;; mention it. i'm leaving it in as a comment for now, in case
> + ;; something breaks.
> + ;; (search-path-specification
> + ;; (variable "CHICKEN_INCLUDE_PATH")
> + ;; (files '("share")))
I think you can remove the comment here; presumably we now know that
CHICKEN_REPOSITORY_PATH is the one that matters. :-)
Could you please ensure that earlier comments notably at
<https://issues.guix.gnu.org/43976#1> have been taken into account, that
the SRFI packages still build and have a layout consistent with the
var/lib/chicken/11 search path above, and send a v2 of the whole series?
Thanks in advance!
Ludo’.
next prev parent reply other threads:[~2020-11-27 9:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-13 8:52 [bug#43976] [PATCH] Chicken build system + some example eggs raingloom
2020-10-18 16:10 ` Ludovic Courtès
2020-11-20 4:51 ` raingloom
2020-11-21 11:23 ` Ludovic Courtès
2020-11-21 20:45 ` raingloom
2020-11-21 20:58 ` Efraim Flashner
2020-11-21 22:13 ` raingloom
2020-11-22 23:12 ` raingloom
2020-11-24 20:22 ` raingloom
2020-11-27 9:09 ` Ludovic Courtès [this message]
2020-12-01 4:14 ` raingloom
2020-12-03 16:04 ` bug#43976: " Ludovic Courtès
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=87eekfxj1y.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=43976@debbugs.gnu.org \
--cc=raingloom@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).