unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Stewart Smith <stewart@flamingspork.com>
To: Alexander Botero-Lowry <alex.boterolowry@gmail.com>
Cc: notmuch@notmuchmail.org
Subject: Re: Mac OS X/Darwin compatibility issues
Date: Thu, 19 Nov 2009 16:42:42 +1100	[thread overview]
Message-ID: <20091119054242.GA11080@flamingspork.com> (raw)
In-Reply-To: <86vdh7cqet.fsf@fortitudo.i-did-not-set--mail-host-address--so-tickle-me>

On Wed, Nov 18, 2009 at 04:24:42PM -0800, Alexander Botero-Lowry wrote:
> On Thu, 19 Nov 2009 10:45:28 +1100, Stewart Smith <stewart@flamingspork.com> wrote:
> > On Wed, Nov 18, 2009 at 11:27:20PM +0100, Carl Worth wrote:
> > > Yes. I knew I was "cheating" by using some GNU extensions here. I'm
> > > happy to accept portability patches for these things, but it's hard for
> > > me to get excited about writing them myself.
> > > 
> > > Care to take a whack at these?
> > 
> > http://www.gnu.org/software/gnulib/
> > 
> > could be a partial answer.
> > 
> Why add yet another dependency for a couple of functions? Especially
> considering how notmuch already depends on glib which includes portability
> functions for various things.

The idea with gnulib (at least what we've done with drizzle) is to
just copy the bits you need into the tree. Does work pretty well for
those small things that you just don't need to depend on a giant like
glib for.
-- 
Stewart Smith

  reply	other threads:[~2009-11-19  5:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-18  3:50 Mac OS X/Darwin compatibility issues Jjgod Jiang
2009-11-18  5:45 ` Alexander Botero-Lowry
2009-11-18  6:14   ` Jjgod Jiang
2009-11-18  6:19     ` Alexander Botero-Lowry
2009-11-18 22:27 ` Carl Worth
2009-11-18 23:45   ` Stewart Smith
2009-11-19  0:24     ` Alexander Botero-Lowry
2009-11-19  5:42       ` Stewart Smith [this message]
2009-11-19 11:34         ` 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=20091119054242.GA11080@flamingspork.com \
    --to=stewart@flamingspork.com \
    --cc=alex.boterolowry@gmail.com \
    --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).