From: ludo@gnu.org (Ludovic Courtès)
To: John J Foerch <jjfoerch@earthlink.net>
Cc: help-guix@gnu.org
Subject: Re: chicken scheme
Date: Sun, 17 Jul 2016 19:45:19 +0200 [thread overview]
Message-ID: <877fck2m6o.fsf@gnu.org> (raw)
In-Reply-To: <87twfo8htp.fsf@hecubus.retroj.net> (John J. Foerch's message of "Sun, 17 Jul 2016 10:22:58 -0400")
Hello!
John J Foerch <jjfoerch@earthlink.net> skribis:
> I'm finally getting back to this. One point about chicken is that it
> does not support multiple extension directories, only one. They go into
> <VARDIR>/chicken/<BINARY-VERSION>. This introduces a difficulty because
> if VARDIR is /var/lib, then the default extensions (that come with
> chicken) get installed to a global directory. The chicken-install
> system will then work, but in the future when we add a package importer,
> imported packages would also go into this global directory.
>
> If on the other hand, VARDIR is (string-append out "/var/lib") the
> default extensions and imported extensions go to the right place, but
> manual chicken-install cannot write to that location.
>
> Any further thoughts on this, given that information?
Ouch, that’s a problem.
Nixpkgs uses VARDIR=OUT/var/lib, meaning that chicken-install does not
work.
However, it also contains an optional patch that allows extensions to be
searched for elsewhere:
https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/compilers/chicken/0001-Introduce-CHICKEN_REPOSITORY_EXTRA.patch
I think the best course of action would be to submit this change
upstream, if it hasn’t been done already. It’s useful beyond Nix and
Guix, so it probably makes sense to include it.
In the meantime, I would (temporarily) sacrifice chicken-install in
favor of an Egg importer.
WDYT?
Thanks,
Ludo’.
next prev parent reply other threads:[~2016-07-17 17:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 19:11 chicken scheme John J Foerch
2016-06-30 21:27 ` Ludovic Courtès
2016-06-30 21:43 ` John J Foerch
2016-07-01 9:36 ` Ludovic Courtès
2016-07-01 12:11 ` John J Foerch
2016-07-01 13:27 ` Thompson, David
2016-07-01 19:52 ` Ludovic Courtès
2016-07-01 20:22 ` John J Foerch
2016-07-02 10:21 ` Ludovic Courtès
2016-07-17 14:22 ` John J Foerch
2016-07-17 17:45 ` Ludovic Courtès [this message]
2016-06-30 22:05 ` John J Foerch
2016-07-01 9:39 ` Ludovic Courtès
2016-07-01 12:16 ` John J Foerch
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=877fck2m6o.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=help-guix@gnu.org \
--cc=jjfoerch@earthlink.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.
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).