From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: chicken scheme Date: Sat, 02 Jul 2016 12:21:08 +0200 Message-ID: <87y45kibmz.fsf@gnu.org> References: <871t3ecx0f.fsf@hecubus.retroj.net> <87shvumkp0.fsf@gnu.org> <87vb0qbbeu.fsf@hecubus.retroj.net> <87ziq1lmyn.fsf@gnu.org> <87h9c9blso.fsf@hecubus.retroj.net> <874m89kufq.fsf@gnu.org> <8737ntaz1c.fsf@hecubus.retroj.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:37055) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bJI32-0002rs-L3 for help-guix@gnu.org; Sat, 02 Jul 2016 06:21:17 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bJI2y-0002Xg-9S for help-guix@gnu.org; Sat, 02 Jul 2016 06:21:15 -0400 In-Reply-To: <8737ntaz1c.fsf@hecubus.retroj.net> (John J. Foerch's message of "Fri, 01 Jul 2016 16:22:55 -0400") List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: John J Foerch Cc: help-guix@gnu.org John J Foerch skribis: > ludo@gnu.org (Ludovic Court=C3=A8s) writes: > >> John J Foerch 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" skribis: >> >>> On Fri, Jul 1, 2016 at 8:11 AM, John J Foerch = 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 =E2=80=98chicken=E2=80=99 package so that =E2=80= =98chicken-install=E2=80=99 >> 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=E2=80=99s best as a user to have all the packages managed b= y the >> same tool, especially if that provides isolation, transactional upgrades >> and rollbacks, etc. >> >> #1 is useful for CHICKEN users who are used to =E2=80=98chicken-install= =E2=80=99 >> (similarly pip, npm, etc. are supposed to work.) It should work in the >> same way as on other distros. I=E2=80=99ve never used it though, so I c= an=E2=80=99t >> give precise advice. >> > > It installs all extensions to a single system-wide directory, with one > path component that gives the binary version. On my debian machine, > that is /var/lib/chicken/7 (for chicken 4.10.0). In that way, it is > simpler than something like npm. Right. So to address #1, we should make sure it uses /var/lib, as discussed earlier. Thanks, Ludo=E2=80=99.