From: Arun Isaac <arunisaac@systemreboot.net>
To: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: guile-dbi from guix not working
Date: Sun, 29 May 2022 13:27:23 +0530 [thread overview]
Message-ID: <875yloepp8.fsf@systemreboot.net> (raw)
In-Reply-To: <3d8782db-68e8-eab7-03d4-852759e96d2f@posteo.de>
Hi Zelphir,
> Should guile-dbd-sqlite3 not be a dependency of guile-dbi then? But on
> the other hand, what if one only wanted to interact with one database
> type and not the other? So maybe not a must have dependency
> then. Hm. What is the typical Guix solution for this kind of
> "specialization" of a library? I think in the Python world, in
> requirements files it would be something like `library[specialization]
> == version`, to install that variant.
You can think of guile-dbd-* as plugins for guile-dbi. So, you install
guile-dbi along with whatever plugins you want for guile-dbi. It's no
different from installing emacs and installing emacs packages of
interest. I don't think we need a special Guix feature for this.
But, guile-dbi should be fixed to produce a proper error message that a
required plugin is missing. It should not produce misleading error
messages like "file not found". If you're up for it, you can try
reporting this to guile-dbi upstream.
Cheers!
Arun
next prev parent reply other threads:[~2022-05-29 8:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-07 11:26 guile-dbi from guix not working Zelphir Kaltstahl
2022-05-07 18:44 ` Luis Felipe
2022-05-08 12:33 ` Zelphir Kaltstahl
2022-05-25 19:18 ` Arun Isaac
2022-05-28 16:37 ` Zelphir Kaltstahl
2022-05-29 7:57 ` Arun Isaac [this message]
2022-05-29 8:58 ` non-input dependencies Was: " raingloom
2022-05-29 14:42 ` Zelphir Kaltstahl
2022-05-29 15:23 ` raingloom
2022-05-30 6:31 ` Arun Isaac
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=875yloepp8.fsf@systemreboot.net \
--to=arunisaac@systemreboot.net \
--cc=help-guix@gnu.org \
--cc=zelphirkaltstahl@posteo.de \
/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).