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: Sat, 21 Nov 2020 12:23:30 +0100 [thread overview]
Message-ID: <87k0ufc5sd.fsf@gnu.org> (raw)
In-Reply-To: <20201120055117.7cb76230@riseup.net> (raingloom@riseup.net's message of "Fri, 20 Nov 2020 05:51:17 +0100")
Hi,
raingloom <raingloom@riseup.net> skribis:
> Well, CHICKEN_IMPORT_PATH seems to just be some kind of historical
> baggage, at least as far as I can tell. It is not mentioned anywhere on
> https://wiki.call-cc.org/man/5 and from what I deciphered from the
> sources, the only time it's used it gets prepended to
> CHICKEN_REPOSITORY_PATH.
>
> I removed the search path and things still seem to work. It was
> probably used in earlier version of Chicken and Nix just never removed
> it. Didn't find any related issues either.
> I think I'll comment it out for now but leave it in? If there are no
> issues with it a few months after merging, it can probably be deleted
> entirely...
I’m not familiar with Chicken. The only advice I could give is to refer
to the Chicken documentation before checking how other distros do it,
it’s probably safer.
> Possibly more important: I noticed some warnings in some builds about
> cp(1). So far it hasn't caused any issues. Gonna fix this, then I think
> it'll be mergeable.
Yup weird.
Anyway, let me know when you have a v2!
Thanks,
Ludo’.
next prev parent reply other threads:[~2020-11-21 11:24 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 [this message]
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
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=87k0ufc5sd.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).