Re: ASDF Builder (Common Lisp) & "package-inferred-system" Packages

[Pierre Neidhardt]

Katherine Cox-Buday <address@hidden> 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 loaded.



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!

-- 
Pierre Neidhardt
https://ambrevar.xyz/

signature.asc
Description: PGP signature