From: ludo@gnu.org (Ludovic Courtès)
To: John J Foerch <jjfoerch@earthlink.net>
Cc: help-guix@gnu.org
Subject: Re: chicken scheme
Date: Fri, 01 Jul 2016 21:52:09 +0200 [thread overview]
Message-ID: <874m89kufq.fsf@gnu.org> (raw)
In-Reply-To: <87h9c9blso.fsf@hecubus.retroj.net> (John J. Foerch's message of "Fri, 01 Jul 2016 08:11:19 -0400")
John J Foerch <jjfoerch@earthlink.net> skribis:
> 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.
"Thompson, David" <dthompson2@worcester.edu> skribis:
> On Fri, Jul 1, 2016 at 8:11 AM, John J Foerch <jjfoerch@earthlink.net> wrote:
>
>> 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?
>
> Yes, but this program is not Guix. It's a completely separate package
> manager, and it should work as intended.
Agreed. So I think there are two issues at hand:
1. How to arrange our ‘chicken’ package so that ‘chicken-install’
works as intended.
2. How to import Eggs so that they can be first-class Guix packages.
#2, which means writing an importer, is definitely the most profitable
approach: It’s best as a user to have all the packages managed by the
same tool, especially if that provides isolation, transactional upgrades
and rollbacks, etc.
#1 is useful for CHICKEN users who are used to ‘chicken-install’
(similarly pip, npm, etc. are supposed to work.) It should work in the
same way as on other distros. I’ve never used it though, so I can’t
give precise advice.
Thanks,
Ludo’.
next prev parent reply other threads:[~2016-07-01 19:52 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 [this message]
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=874m89kufq.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).