From: Carl Worth <cworth@cworth.org>
To: Stewart Smith <stewart@flamingspork.com>, Alexander Botero-Lowry
	<alex.boterolowry@gmail.com>
In-Reply-To: <20091119054242.GA11080@flamingspork.com>
References: <ddd65cda0911171950o4eea4389v86de9525e46052d3@mail.gmail.com>
	<874oorfozb.fsf@yoom.home.cworth.org>
	<20091118234527.GO9315@flamingspork.com>
	<86vdh7cqet.fsf@fortitudo.i-did-not-set--mail-host-address--so-tickle-me>
	<20091119054242.GA11080@flamingspork.com>
Date: Thu, 19 Nov 2009 12:34:56 +0100
Message-ID: <877htmsq73.fsf@yoom.home.cworth.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: notmuch@notmuchmail.org
Subject: Re: [notmuch] Mac OS X/Darwin compatibility issues
Precedence: list

On Thu, 19 Nov 2009 16:42:42 +1100, Stewart Smith <stewart@flamingspork.com> wrote:
> 
> 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.

Looks like that's the intended mode of usage for gnulib:

	Its components are intended to be shared at the source level, rather
	than being a library that gets built, installed, and linked against.
	Thus, there is no distribution tarball; the idea is to copy files from
	Gnulib into your own source tree.

That does sound like exactly what we need for getting portable
implementations of the few GNU-extension functions we're using here.

So thanks for sharing this.

-Carl