all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Katherine Cox-Buday <cox.katherine.e@gmail.com>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: 35991@debbugs.gnu.org
Subject: [bug#35991] [PATCH 0/9] Packaging sbcl-iolib (and dbus)
Date: Tue, 04 Jun 2019 07:50:39 -0500	[thread overview]
Message-ID: <87ftoph5uo.fsf@gmail.com> (raw)
In-Reply-To: <20190529132917.7142-1-mail@ambrevar.xyz> (Pierre Neidhardt's message of "Wed, 29 May 2019 15:29:17 +0200")

Pierre Neidhardt <mail@ambrevar.xyz> writes:

> I can build iolib but the dbus package fails to use it because
> iolib-multiplex, a subsystem, cannot be found.
>
> Indeed, the sbcl package only exposes iolib while the .asd in the source exposes a dozen of subsystems, including
> :iolib/multiplex.
>
> See https://github.com/sionescu/iolib/blob/master/iolib.asd.
>
> Do we support multi-system .asd files?

Hey Pierre, I apologize for taking a bit to get back.

As far as I'm aware, we don't automatically support multiple systems in
a single asd file. With ASDF now supporting package-inferred systems,
which introduces the concept of "inferred" systems which are not even
declared in an asd file, I believe we need to shore up how Guix handles
CL systems. Unfortunately I haven't had the time to check my math on my
proposal and submit it to the list. Ironically I have done more
packaging of CL systems instead (I needed them!).

However, I think this case can still be handled with our current setup.
What I would try is to define your base package, and then define all the
subsequent packages as having inherited from the base package, but
exposing the correct ASDF system. I don't think this will cause any
unecessary compilation as the ASDF systems declare which files are
required.

I'll be interested to know if this works.

-- 
Katherine

  parent reply	other threads:[~2019-06-04 12:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-29 13:29 [bug#35991] [PATCH 0/9] Packaging sbcl-iolib (and dbus) Pierre Neidhardt
2019-05-29 13:29 ` [bug#35985] [PATCH 1/9] gnu: Add idna Pierre Neidhardt
2019-05-29 13:29   ` [bug#35984] [PATCH 2/9] gnu: Add swap-bytes Pierre Neidhardt
2019-05-29 13:29   ` [bug#35989] [PATCH 3/9] gnu: Add sbcl-iolib.asdf Pierre Neidhardt
2019-05-29 13:29   ` [bug#35986] [PATCH 4/9] gnu: Add sbcl-iolib.conf Pierre Neidhardt
2019-05-29 13:29   ` [bug#35988] [PATCH 5/9] gnu: Add sbcl-iolib.common-lisp Pierre Neidhardt
2019-05-29 13:29   ` [bug#35987] [PATCH 6/9] gnu: Add sbcl-iolib.base Pierre Neidhardt
2019-05-29 13:29   ` [bug#35983] [PATCH 7/9] gnu: Add sbcl-iolib.grovel Pierre Neidhardt
2019-05-29 13:29   ` [bug#35982] [PATCH 8/9] gnu: Add sbcl-iolib Pierre Neidhardt
2019-05-29 13:29   ` [bug#35990] [PATCH 9/9] gnu: Add sbcl-dbus Pierre Neidhardt
2019-05-29 14:07 ` [bug#35991] [PATCH 1/9] gnu: Add idna Pierre Neidhardt
2019-05-29 14:07   ` [bug#35991] [PATCH 2/9] gnu: Add swap-bytes Pierre Neidhardt
2019-05-29 14:07   ` [bug#35991] [PATCH 3/9] gnu: Add sbcl-iolib.asdf Pierre Neidhardt
2019-05-29 14:07   ` [bug#35991] [PATCH 4/9] gnu: Add sbcl-iolib.conf Pierre Neidhardt
2019-05-29 14:07   ` [bug#35991] [PATCH 5/9] gnu: Add sbcl-iolib.common-lisp Pierre Neidhardt
2019-05-29 14:07   ` [bug#35991] [PATCH 6/9] gnu: Add sbcl-iolib.base Pierre Neidhardt
2019-05-29 14:07   ` [bug#35991] [PATCH 7/9] gnu: Add sbcl-iolib.grovel Pierre Neidhardt
2019-05-29 14:07   ` [bug#35991] [PATCH 8/9] gnu: Add sbcl-iolib Pierre Neidhardt
2019-05-29 14:07   ` [bug#35991] [PATCH 9/9] gnu: Add sbcl-dbus Pierre Neidhardt
2019-06-04 12:50 ` Katherine Cox-Buday [this message]
2019-06-26  8:30   ` [bug#35991] [PATCH 0/9] Packaging sbcl-iolib (and dbus) 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ftoph5uo.fsf@gmail.com \
    --to=cox.katherine.e@gmail.com \
    --cc=35991@debbugs.gnu.org \
    --cc=mail@ambrevar.xyz \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.