From: "Simen Endsjø" <simendsjo@gmail.com>
To: help-guix@gnu.org
Subject: Common Lisp systems using `package-inferred-system' fails to find dependency
Date: Wed, 30 Aug 2023 15:26:50 +0200 [thread overview]
Message-ID: <87ttsgbqws.fsf@gmail.com> (raw)
Hi,
I’m trying to package some Common Lisp projects which is using
package-inferred-system, but I’m not really sure how this should be done.
I get into a problem packaging log4cl-extras, which has the system
log4cl-extras/error, which in turn uses dissect.
Adding `(inputs (list cl-dissect ...))' doesn’t work, and still gives an error:
┌────
│ Component dissect not found, required by
│ #<PACKAGE-INFERRED-SYSTEM "log4cl-extras/error">
└────
So I probably need to package these in some other way? These projects are using
<https://github.com/40ants/40ants-asdf-system> if that makes a difference.
Any pointers in the right direction would be appreciated.
┌────
│ (define-public sbcl-log4cl-extras
│ (let ((commit "920e5e551b116419aa82de46e4a8a0f787db7d82")
│ (revision "0"))
│ (package
│ (name "sbcl-log4cl-extras")
│ (version (git-version "0.9.0" revision commit))
│ (source
│ (origin
│ (method git-fetch)
│ (uri (git-reference
│ (url "https://github.com/40ants/log4cl-extras")
│ (commit commit)))
│ (sha256
│ (base32 "0nhzsh9sm19kd6nwn8k4j8rkfpjnkfx3i30zqr2kvjs0h27ljpjy"))))
│ (build-system asdf-build-system/sbcl)
│ (arguments
│ ;; Drop tests to avoid package more packages
│ '(#:tests? #f))
│ (native-inputs
│ (list))
│ (inputs
│ (list
│ cl-40ants-asdf-system
│ cl-pythonic-string-reader
│ cl-log4cl
│ cl-jonathan
│ cl-40ants-doc
│ cl-strings
│ cl-global-vars
│ cl-dissect
│ cl-with-output-to-stream))
│ (home-page "https://40ants.com/log4cl-extras")
│ (synopsis "A bunch of addons to LOG4CL: JSON appender, context fields, cross-finger appender, etc.")
│ (description
│ "This library extends LOG4CL system in a few ways:
│
│ * It helps with configuration of multiple appenders and layouts.
│ * Has a facility to catch context fields and to log them.
│ * Has a macro to log unhandled errors.
│ * Adds a layout to write messages as JSON, which is useful for production as makes easier to parse and process such logs.
│ * Uses the appenders which are not disabled in case of some error which again, should be useful for production.")
│ (license license:bsd-4))))
└────
next reply other threads:[~2023-08-30 13:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 13:26 Simen Endsjø [this message]
2023-09-04 8:00 ` Common Lisp systems using `package-inferred-system' fails to find dependency Guillaume Le Vaillant
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=87ttsgbqws.fsf@gmail.com \
--to=simendsjo@gmail.com \
--cc=help-guix@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.
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).