From: ludo@gnu.org (Ludovic Courtès)
To: 宋文武 <iyzsong@member.fsf.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH]: gnu: Add guile-dbi.
Date: Mon, 20 Jun 2016 10:24:47 +0200 [thread overview]
Message-ID: <878ty06ze8.fsf@gnu.org> (raw)
In-Reply-To: <87bn2yc3zu.fsf@member.fsf.org> ("宋文武"'s message of "Sat, 18 Jun 2016 16:09:41 +0800")
iyzsong@member.fsf.org (宋文武) skribis:
> From 8e73c3e1a798b134e341c71c4b1c17d60956e3d5 Mon Sep 17 00:00:00 2001
> From: =?UTF-8?q?=E5=AE=8B=E6=96=87=E6=AD=A6?= <iyzsong@gmail.com>
> Date: Fri, 17 Jun 2016 22:44:56 +0800
> Subject: [PATCH 1/2] gnu: Add guile-dbi.
>
> * gnu/packages/guile.scm (guile-dbi): New variable.
LGTM!
> From 87c3ef658e24035715b48606fb9ef24d55aaddfa Mon Sep 17 00:00:00 2001
> From: =?UTF-8?q?=E5=AE=8B=E6=96=87=E6=AD=A6?= <iyzsong@gmail.com>
> Date: Sat, 18 Jun 2016 15:49:36 +0800
> Subject: [PATCH 2/2] gnu: Add guile-dbd-sqlite3.
>
> * gnu/packages/guile.scm (guile-dbd-sqlite3): New variable.
LGTM.
> Unfortunately, Guile DBI loads its backends using `dlopen',
> so I have to set 'LD_LIBRARY_PATH' to '$guile-dbd-sqlite/lib'
> for loading it.
I don’t have any great ideas.
If it uses lt_dlopen, then we should recommend setting LTDL_LIBRARY_PATH
instead of LD_LIBRARY_PATH, which is a lesser evil.
Otherwise, we could also hard-code the file name of, say,
guile-dbd-sqlite in guile-dbi, such that there’s always at least one
backend available.
WDYT?
Thanks,
Ludo’.
next prev parent reply other threads:[~2016-06-20 8:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-18 8:09 [PATCH]: gnu: Add guile-dbi 宋文武
2016-06-20 8:24 ` Ludovic Courtès [this message]
2016-06-21 8:35 ` Maurizio Boriani
2016-06-21 14:14 ` Ludovic Courtès
2016-06-21 15:09 ` 宋文武
2016-06-21 20:56 ` Ludovic Courtès
2016-09-16 3:36 ` guile-dbi: Use libltdl and prefer GUILE_DBD_PATH 宋文武
2016-09-16 6:57 ` baux
2017-07-10 22:54 ` Linas Vepstas
2017-07-11 11:02 ` 宋文武
2017-07-11 18:31 ` Nala Ginrut
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=878ty06ze8.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=iyzsong@member.fsf.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 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.