From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Katherine Cox-Buday <cox.katherine.e@gmail.com>,
Andy Patterson <ajpatter@uwaterloo.ca>
Cc: guix-devel@gnu.org
Subject: Re: ASDF Builder (Common Lisp) & "package-inferred-system" Packages
Date: Fri, 02 Aug 2019 18:28:34 +0200 [thread overview]
Message-ID: <874l2zv8el.fsf@ambrevar.xyz> (raw)
In-Reply-To: <87h8ec6qek.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3057 bytes --]
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-channel
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:
--8<---------------cut here---------------start------------->8---
Unhandled ASDF/ACTION:CIRCULAR-DEPENDENCY in thread #<SB-THREAD:THREAD "main thread" RUNNING
{10005385B3}>:
Circular dependency:
((#<ASDF/LISP-ACTION:LOAD-OP >
. #<ASDF/PACKAGE-INFERRED-SYSTEM:PACKAGE-INFERRED-SYSTEM "dbus">)
(#<ASDF/LISP-ACTION:PREPARE-OP >
. #<ASDF/PACKAGE-INFERRED-SYSTEM:PACKAGE-INFERRED-SYSTEM "dbus">)
(#<ASDF/LISP-ACTION:LOAD-OP >
. #<ASDF/PACKAGE-INFERRED-SYSTEM:PACKAGE-INFERRED-SYSTEM "dbus/all">)
(#<ASDF/LISP-ACTION:LOAD-OP >
. #<ASDF/LISP-ACTION:CL-SOURCE-FILE "dbus/all" "lisp">)
(#<ASDF/LISP-ACTION:PREPARE-OP >
. #<ASDF/LISP-ACTION:CL-SOURCE-FILE "dbus/all" "lisp">)
(#<ASDF/LISP-ACTION:PREPARE-OP >
. #<ASDF/PACKAGE-INFERRED-SYSTEM:PACKAGE-INFERRED-SYSTEM "dbus/all">)
(#<ASDF/LISP-ACTION:LOAD-OP >
. #<ASDF/PACKAGE-INFERRED-SYSTEM:PACKAGE-INFERRED-SYSTEM "dbus/convenience">)
(#<ASDF/LISP-ACTION:LOAD-OP >
. #<ASDF/LISP-ACTION:CL-SOURCE-FILE "dbus/convenience" "lisp">)
(#<ASDF/LISP-ACTION:PREPARE-OP >
. #<ASDF/LISP-ACTION:CL-SOURCE-FILE "dbus/convenience" "lisp">)
(#<ASDF/LISP-ACTION:PREPARE-OP >
. #<ASDF/PACKAGE-INFERRED-SYSTEM:PACKAGE-INFERRED-SYSTEM "dbus/convenience">)
(#<ASDF/LISP-ACTION:LOAD-OP >
. #<ASDF/PACKAGE-INFERRED-SYSTEM:PACKAGE-INFERRED-SYSTEM "dbus/publish">)
(#<ASDF/LISP-ACTION:LOAD-OP >
. #<ASDF/LISP-ACTION:CL-SOURCE-FILE "dbus/publish" "lisp">)
(#<ASDF/LISP-ACTION:PREPARE-OP >
. #<ASDF/LISP-ACTION:CL-SOURCE-FILE "dbus/publish" "lisp">)
(#<ASDF/LISP-ACTION:PREPARE-OP >
. #<ASDF/PACKAGE-INFERRED-SYSTEM:PACKAGE-INFERRED-SYSTEM "dbus/publish">))
--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?
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-08-02 16:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 0:25 ASDF Builder (Common Lisp) & "package-inferred-system" Packages Katherine Cox-Buday
2019-01-11 9:01 ` Pierre Neidhardt
2019-01-11 15:34 ` Katherine Cox-Buday
2019-01-12 20:24 ` Katherine Cox-Buday
2019-01-13 19:14 ` Andy Patterson
2019-01-14 0:20 ` Katherine Cox-Buday
2019-08-02 16:28 ` Pierre Neidhardt [this message]
2019-08-02 16:43 ` Pierre Neidhardt
2019-08-02 17:37 ` Pierre Neidhardt
2019-08-02 20:27 ` Katherine Cox-Buday
2019-08-03 8:04 ` Pierre Neidhardt
2019-08-03 8:44 ` Pierre Neidhardt
2019-08-03 14:14 ` Katherine Cox-Buday
2019-08-06 10:41 ` Pierre Neidhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874l2zv8el.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=ajpatter@uwaterloo.ca \
--cc=cox.katherine.e@gmail.com \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).