From: Carl Worth <cworth@cworth.org>
To: notmuch@notmuchmail.org
Subject: My repository is moving once again...
Date: Fri, 04 Jun 2010 17:32:43 -0700 [thread overview]
Message-ID: <87typiz5ck.fsf@yoom.home.cworth.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2436 bytes --]
After a (much-too-long) hiatus, I just pushed a batch of changes to my
notmuch repository.
This includes the several changes that I recently reviewed on the
mailing list and said that I had committed locally and would push soon.
Additionally, I've pushed a few of bug fixes as follows:
* Fix to never add a partially complete message to the database.
Various interruptions to notmuch processing, (perhaps other bugs
described below) would leave a half-complete message in the
database. And later runs of notmuch would trip and fall over on this
half-complete message. Thanks to a suggestion from Olly, notmuch now
never adds the partial documents to the database so this problem
should be avoided entirely.
* Fix for really long message ID values.
Scott mentioned various Xapian exceptions and notmuch internal
errors that occurred after trying to add a message with a 300+
character message ID. I've fixed this to now be handled well, (with
new tests in the test suite to handle 512-character message IDs).
* Make things easier after "make install" (for Linux at least)
On Linux systems, the configure script will now identify the various
paths supported by ldconfig (such as /usr/local/lib). Then, if the
prefix is to one of these places (such as /usr/local/), make install
will run ldconfig automatically. This will allow some people to be
able to more easily run notmuch immediately after installing.
Similarly, if the notmuch library is installed to some non-system
directory, (such as --prefix=${HOME}/foo), then the final link of
the shared binary will include a DT_RUNPATH entry to the directory
in which the library is installed. This will also allow the notmuch
binary to work immediately after "make install" without the user
needing to set the LD_LIBRARY_PATH variable.
I implemented this last piece only on Linux. I think OS X doesn't need
additional support for this since linking binaries against libraries
might automatically encode the paths, (though I haven't tested). I also
haven't investigated what might be the right thing to do for Solaris,
(it's probably not all that different than what I did for Linux).
So if anybody wants to put together similar patches as needed for their
favorite platforms, then that would be great.
-Carl
--
carl.d.worth@intel.com
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2010-06-05 0:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-05 0:32 Carl Worth [this message]
2010-06-07 7:47 ` My repository is moving once again Michal Sojka
2010-06-07 15:10 ` 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=87typiz5ck.fsf@yoom.home.cworth.org \
--to=cworth@cworth.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).