From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pierre Neidhardt Subject: Re: ASDF Builder (Common Lisp) & "package-inferred-system" Packages Date: Tue, 06 Aug 2019 12:41:18 +0200 Message-ID: <87mugmzicx.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> <874l2zv8el.fsf@ambrevar.xyz> <87ef238g8t.fsf@gmail.com> <87sgqiu11w.fsf@ambrevar.xyz> <87r26272va.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]:44957) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1huwuC-0004cW-8x for guix-devel@gnu.org; Tue, 06 Aug 2019 06:41:25 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1huwuB-0007RO-63 for guix-devel@gnu.org; Tue, 06 Aug 2019 06:41:24 -0400 Received: from relay10.mail.gandi.net ([217.70.178.230]:43239) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1huwuB-0007Qt-00 for guix-devel@gnu.org; Tue, 06 Aug 2019 06:41:23 -0400 In-Reply-To: <87r26272va.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 Cc: guix-devel@gnu.org --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Katherine Cox-Buday writes: > I never got this to work[1]. I think Ningle's systems are being bundled > into a single fasl, but for whatever reason, its subsystems cannot be > found despite that bundled fasl being on the path. According to Fare in the GitLab discussion, this is to be expected. It seems that generally fasls cannot be bundled for inferred packages. > Last I looked at this, I remember being left with the distinct > impression that we would have to stop producing system fasls, and rather > than having one directory of system fasls, we'd have a tree of system > directories, each populated with all the fasls for a system e.g.: > > - ~/.guix-profile/lib/sbcl/ > - dbus/ > - dbus-all.fasl > - dbus-utils.fasl > - ... > > And then find a way to search ~/.guix-profile/lib/sbcl/ recursively. The > ASDF manual says[2] $XDG_CONFIG_DIRS/common-lisp/source-registry.conf > can hold configurations, as well as `CL_SOURCE_REGISTRY`. Maybe Guix > could set one of these in the profile to something like `(:tree > (:home ".guix-profile/lib/sbcl/"))`. > > Or we could stick to the `*source-registry*` variable and use a smarter > Common Lisp function to populate it. My current understanding is that *source-registry* is the ideal way to go. So we would just need to add the /lib/sbcl folder and that should be enough? As far as I understand, that's how the ~/.cache/common-lisp fasls are loade= d. This is not too urgent for me anymore since cl-dbus works (source), so I might only work on this when I have more time in the future. Cheers! =2D-=20 Pierre Neidhardt https://ambrevar.xyz/ --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEUPM+LlsMPZAEJKvom9z0l6S7zH8FAl1JWU4ACgkQm9z0l6S7 zH+shQf+I0/KA+i5sPlyptond1bYPPnEfFlJRwRy+DfT1PgFh4plNQn1aQ4hnTRS uZJTAKqweu+zfPhEfFsDIGWBrIzCt1OVDm0yRS6ZhbIm8TAfmDJVSvZVyTRU/Pq+ cOoAP5eNCBgdKJfAkSQm7LG6kUeTk6bT0hu/hQvWwgLa064A8fABpl50SQgLE9cN twzpL7d50YE+bUEO36J2tskeqCm48PfbFcNL6XhuUWDlrnz0g2uN7ZaUT3CbrZV/ F6xwEK6Xv7fPm0/G76cyNs403qb0e8a4beJ1YFZ3xQ0wolFEY9xAEVvtqtKQXj5c bR7oiYqm8irWta5qd7Rx62Y0IuptXA== =LJ/Y -----END PGP SIGNATURE----- --=-=-=--