From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dimakakos Dimos Subject: Re: Racket packages: formerly Move DrRacket to a separate output? Date: Wed, 19 Feb 2020 21:55:22 +0200 Message-ID: <874kvmtkr9.fsf@bendersteed.tech> References: <87efdx6nzt.fsf@ambrevar.xyz> <87pnxgjwfx.fsf@gnu.org> <87bm90rn22.fsf@dustycloud.org> <20191004154658.5jswjutbcfe6zsig@thebird.nl> <875zl471sp.fsf@dustycloud.org> <877e5k1671.fsf@gmail.com> <87o8yudpcr.fsf@gnu.org> <875zg3ri9s.fsf@ambrevar.xyz> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:45824) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j4VWO-0006qm-4f for guix-devel@gnu.org; Wed, 19 Feb 2020 15:00:37 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1j4VWM-0006kt-WA for guix-devel@gnu.org; Wed, 19 Feb 2020 15:00:35 -0500 Received: from m32-15.eu.mailgun.net ([141.193.32.15]:58353) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1j4VWM-0006iZ-39 for guix-devel@gnu.org; Wed, 19 Feb 2020 15:00:34 -0500 In-reply-to: <875zg3ri9s.fsf@ambrevar.xyz> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org Sender: "Guix-devel" To: guix-devel@gnu.org Pierre Neidhardt writes: > I've (finally) pushed racket-minimal. > Hooray! > > Now to the Racket importer... Anyone? > Dimakakos? :) Nice! It will be very useful. I've put some research into a build system for racket, and sadly it isn't trivial to match the racket package system to guix. There is a lot of state handling in racket specific files, since every package is indexed by linking the specific folder of a package. Right now I'm creating these files ad-hoc but it doens't seem the best approach, since racket is really slow searching for the dependencies in many folders. At the same time, racket tries sometims to rebuild packages that are passed as inputs. There are also circular dependencies and other stuff that need to be ironed out. I'm also talking with the creator of racket2nix, a similar project for nix and he had the same problems, so we discussed about working for a solution for both package managers. So in conclusion, I don't have a specific roadmap, but I'm still working on it.