From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pierre Neidhardt Subject: Re: ASDF Builder (Common Lisp) & "package-inferred-system" Packages Date: Fri, 02 Aug 2019 18:28:34 +0200 Message-ID: <874l2zv8el.fsf@ambrevar.xyz> References: <8736q082h8.fsf@gmail.com> <87fttzd0uo.fsf@ambrevar.xyz> <87wonb6wdn.fsf@gmail.com> <87lg3p7hfd.fsf@gmail.com> <20190113141426.00360523@mailservices.uwaterloo.ca> <87h8ec6qek.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:37490) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1htaQ4-0002TW-T5 for guix-devel@gnu.org; Fri, 02 Aug 2019 12:28:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1htaQ3-0005To-IL for guix-devel@gnu.org; Fri, 02 Aug 2019 12:28:40 -0400 Received: from relay5-d.mail.gandi.net ([217.70.183.197]:34121) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1htaQ3-0005PL-7c for guix-devel@gnu.org; Fri, 02 Aug 2019 12:28:39 -0400 In-Reply-To: <87h8ec6qek.fsf@gmail.com> 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.org@gnu.org Sender: "Guix-devel" To: Katherine Cox-Buday , Andy Patterson Cc: guix-devel@gnu.org --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi! It's been a while, and now that I'm on the verge of releasing Next 1.3 and a dependency is a package-inferred-system, I thought it would be the perfect time to dig out this issue! :) So I'm trying to package cl-dbus (https://github.com/death/dbus). You'll find the recipes here: https://gitlab.com/atlas-engineer/next-guix-c= hannel I can package it in several ways, but the result does not work for the reasons mentioned in this topic. I thought of the following trick: what about just dumping the full source into "/lib/sbcl"? Wouldn't that work? Do we really need the .fasl files? When I try to build Next with dbus packaged using this last trick, it actually gets quite far, until it complains about circular dependencies: =2D-8<---------------cut here---------------start------------->8--- Unhandled ASDF/ACTION:CIRCULAR-DEPENDENCY in thread #: Circular dependency: ((# . #) (# . #) (# . #) (# . #) (# . #) (# . #) (# . #) (# . #) (# . #) (# . #) (# . #) (# . #) (# . #) (# . #)) =2D-8<---------------cut here---------------end--------------->8--- I've asked for help on ASDF issue tracker: https://gitlab.common-lisp.net/asdf/asdf/issues/10 By the way, there they confirmed that using `*source-registry*` is the right way to go. Note that this is _not_ the same variable as `*source-registry-parameter*` that Katherine mentioned. So we are good on that front. Thoughts? =2D-=20 Pierre Neidhardt https://ambrevar.xyz/ --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEUPM+LlsMPZAEJKvom9z0l6S7zH8FAl1EZLIACgkQm9z0l6S7 zH8wsgf8D9Z0F1iwJ1JngjF/mIbnpTxMBLf2HPdRJcUyLvJatu0giqxHeuM79lJk fkYU6HBQY84c9bW+GZUkELoFKuAzEslXoK8oH9sG9E9b+b7frCsRW4D4QMDKjW1A y+kxOUkmoH2pt/0d1/hNIJ4Zeur2AYhNpyhcPvqW0VYBbkbk4eMA+9LL/mAKurQL lOluCHbu7IASPgefrQQJXIleAOQtTTZmuC99OOcoqN6Ymqtrq64wWWNL9yMZ5Hc4 /OO66sHxzPPJSTsBAqGWdZaAh7WrTLn9RHPwHRuXTt5k8tsFjee/mMipB61qXF7F imRX1Y//e2Bej2+FwBenPUNY504AgA== =fgNH -----END PGP SIGNATURE----- --=-=-=--