From: Ingmar Vanhassel <ingmar@exherbo.org>
To: notmuch <notmuch@notmuchmail.org>
Subject: Re: [PATCH] Use libgcrypt for hashing.
Date: Sat, 28 Nov 2009 04:59:13 +0100 [thread overview]
Message-ID: <1259380562-sup-5175@cannonball> (raw)
In-Reply-To: <87ws1be35o.fsf@vertex.dottedmag>
Excerpts from Mikhail Gusarov's message of Sat Nov 28 04:31:15 +0100 2009:
>
> Twas brillig at 21:28:03 27.11.2009 UTC-06 when jeff@ocjtech.us did gyre and
> gimble:
>
> JCO> Instead of including a private implementation of the SHA1 hash
>
> xserver went this road, and now it has
> --with-sha1=libc|libmd|libgcrypt|libcrypto|libsha1|CommonCrypto in
> configure.
From a distribution & security point of view I'd much rather be able to
choose one hashing library & use that as widely as possible, rather than
having every application ship its own copy.
> JCO> This means less code of our own to maintain and
>
> As libsha1 maintainer I'm volunteering to maintain in-tree copy in
> notmuch :)
Right, but on top of that, it would still be preferable to keep the
option for packagers to use a system library instead.
Most distributions have a rather strict policy to use system libraries
over internal copies.
--
Exherbo KDE, X.org maintainer
next prev parent reply other threads:[~2009-11-28 3:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-28 3:28 [PATCH] Use libgcrypt for hashing Jeffrey C. Ollie
2009-11-28 3:31 ` Mikhail Gusarov
2009-11-28 3:59 ` Ingmar Vanhassel [this message]
2009-11-28 5:43 ` Jeffrey Ollie
2009-11-28 5:52 ` Alexander Botero-Lowry
2009-11-28 5:41 ` Jeffrey Ollie
2009-11-28 6:43 ` Carl Worth
2009-11-28 7:38 ` Jeffrey Ollie
2009-11-28 6:23 ` Carl Worth
2009-11-28 6:22 ` Carl Worth
2010-01-08 20:43 ` micah anderson
2010-01-14 22:16 ` Carl Worth
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1259380562-sup-5175@cannonball \
--to=ingmar@exherbo.org \
--cc=notmuch@notmuchmail.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 public inbox
https://yhetil.org/notmuch.git/
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).