From: John J Foerch <jjfoerch@earthlink.net>
To: help-guix@gnu.org
Subject: Re: chicken scheme
Date: Fri, 01 Jul 2016 08:11:19 -0400 [thread overview]
Message-ID: <87h9c9blso.fsf@hecubus.retroj.net> (raw)
In-Reply-To: 87ziq1lmyn.fsf@gnu.org
ludo@gnu.org (Ludovic Courtès) writes:
> John J Foerch <jjfoerch@earthlink.net> skribis:
>
>> Installing gcc-toolchain helped, and there are no more compilation
>> errors. Another error came up in trying to install the built files.
>> Here is my log:
>>
>> <SNIP>
>
> I think we need to build CHICKEN such that it uses /var/lib instead of
> /gnu/store/…-chicken/var/lib (the latter is immutable.) I suppose
> that’s how it works on other distros, right? (With this approach only
> root can install software, though.)
>
> Do you know how to make this change?
>
> Thanks,
> Ludo’.
First a question about /var/lib, and please excuse the newbie question.
If chicken extensions were installed to /var/lib, wouldn't that go
against the spirit of guix of keeping every program isolated? Isn't
/var/lib global state?
I have just learned about 'guix import', and have the thought that a
package importer would be the better way to go. Eventually I would like
to package software that I've written in CHICKEN for GuixSD, and only a
package importer would make that feasible.
I will definitely give it a try to add such a feature to guix, and will
follow whatever advice you may have. In some ways I am still learning
the very basics of guix, so it may take me a bit to get up to speed.
Thank you,
--
John Foerch
next prev parent reply other threads:[~2016-07-01 12:11 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 [this message]
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
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=87h9c9blso.fsf@hecubus.retroj.net \
--to=jjfoerch@earthlink.net \
--cc=help-guix@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.
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).