From: David Bremner <david@tethera.net>
To: Jani Nikula <jani@nikula.org>, notmuch@notmuchmail.org
Subject: Re: [PATCH] RFC: impliment gzipped output for notmuch dump
Date: Sat, 29 Mar 2014 09:29:15 -0300 [thread overview]
Message-ID: <87ob0pdw84.fsf@zancas.localnet> (raw)
In-Reply-To: <87wqfdbblz.fsf@nikula.org>
Jani Nikula <jani@nikula.org> writes:
> Is it reasonable to require zlib? It's possible to have conditional
> build for this, but it will be laborous to do it cleanly. I could be
> persuaded either way, perhaps more easily to just requiring it.
If I recall correctly, xapian needs zlib. At least on Debian this is a
hard dependency. What is needed additionally is the zlib headers.
> If you do require zlib, the missing dependencies error message from
> configure should include a check for have_zlib and a note about it
> similar to other required dependencies.
good point.
> Also, it would seem natural to support gzipped input in restore as
> well... do you think it would be silly to support gzipped output only
> internally until we've added gzipped input too? This could be in a later
> release in the future.
I couldn't decide which was sillier: to have have gzipped output but not
input, or to leave off the command line argument (it's something like 3
lines of diff). I lean to making it accessible from the CLI to better
support testing.
d
next prev parent reply other threads:[~2014-03-29 12:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 17:07 [PATCH 0/2] cli: notmuch dump abstractions Jani Nikula
2014-03-25 17:07 ` [PATCH 1/2] cli: abstract database dumping from the dump command Jani Nikula
2014-03-25 17:07 ` [PATCH 2/2] cli: abstract dump file open " Jani Nikula
2014-03-25 17:48 ` [PATCH v2] " Jani Nikula
2014-03-26 22:01 ` [PATCH 0/2] cli: notmuch dump abstractions Mark Walters
2014-03-29 1:20 ` [PATCH] RFC: impliment gzipped output for notmuch dump David Bremner
2014-03-29 7:16 ` Tomi Ollila
2014-03-29 9:25 ` Jani Nikula
2014-03-29 12:29 ` David Bremner [this message]
2014-03-29 13:02 ` Jani Nikula
2014-03-29 16:25 ` David Bremner
2014-03-29 13:46 ` [PATCH] dump: support gzipped output David Bremner
2014-03-29 18:16 ` David Bremner
2014-03-29 18:16 ` [Patch v2 1/3] dump: support gzipped output David Bremner
2014-03-29 18:16 ` [Patch v2 2/3] util: add gzreadline David Bremner
2014-03-30 8:30 ` Tomi Ollila
2014-03-30 11:23 ` [Patch v3] " David Bremner
2014-03-30 12:45 ` Tomi Ollila
2014-03-30 14:37 ` David Bremner
2014-03-30 16:13 ` Tomi Ollila
2014-03-30 11:03 ` [Patch v2 2/3] " David Bremner
2014-03-29 18:16 ` [Patch v2 3/3] restore: transparently support gzipped input David Bremner
2014-03-30 22:33 ` [PATCH 0/2] cli: notmuch dump abstractions David Bremner
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=87ob0pdw84.fsf@zancas.localnet \
--to=david@tethera.net \
--cc=jani@nikula.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).