all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: help-guix@gnu.org
Subject: Re: guix edit mutt -- with new option, and dependency, how I got it working
Date: Fri, 11 Mar 2016 14:37:38 +0100	[thread overview]
Message-ID: <87k2l92l0d.fsf@gnu.org> (raw)
In-Reply-To: <20160310213433.GA9444@jasmine> (Leo Famulari's message of "Thu, 10 Mar 2016 16:34:33 -0500")

Leo Famulari <leo@famulari.name> skribis:

> On Thu, Mar 10, 2016 at 11:06:49PM +0200, Efraim Flashner wrote:
>> On Thu, 10 Mar 2016 15:45:51 -0500

[...]

>> > I agree that we should build our Mutt with this option enabled.
>> > 
>> > If everyone agrees, the question is which database to use — we have gdbm
>> > and bdb in our package tree (I think tokyocabinet is a WIP). I have no
>> > idea which database is a better choice. What do people think?
>> 
>> Assuming mutt, gdbm and bdb build on all architectures, comparing guix graph
>> of mutt, gdbm and bdb, and the graph of the two databases is identical. The
>> only other input I have is that debian uses tokyocabinet as a dependancy.
>
> It looks like they both build on all architectures.
>
> Gdbm is a little smaller and it's a GNU project, so I vote for gdbm, in
> the absence of any knowledge of the two databases' technical merits.

+1.

(I wonder how this relates to the subject of this message, though.  ;-))

Ludo’.

      reply	other threads:[~2016-03-11 13:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-10  0:44 guix edit mutt -- with new option, and dependency, how I got it working Jean Louis
2016-03-10  1:45 ` Leo Famulari
2016-03-10  6:58   ` Jean Louis
2016-03-10 20:45     ` Leo Famulari
2016-03-10 21:06       ` Efraim Flashner
2016-03-10 21:34         ` Leo Famulari
2016-03-11 13:37           ` Ludovic Courtès [this message]

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=87k2l92l0d.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=help-guix@gnu.org \
    --cc=leo@famulari.name \
    /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.