From: Carl Worth <cworth@cworth.org>
To: david@tethera.net, notmuch@notmuchmail.org
Subject: Re: [PATCH] libnotmuch: fix typos in CLEAN setting, add file
In-Reply-To: <1309005958-10409-1-git-send-email-david@tethera.net>
References: <87aad7ce2w.fsf@yoom.home.cworth.org>
	<1309005958-10409-1-git-send-email-david@tethera.net>
User-Agent: Notmuch/0.5 (http://notmuchmail.org) Emacs/23.3.1
	(i486-pc-linux-gnu)
Date: Tue, 28 Jun 2011 11:55:20 -0700
Message-ID: <87liwlaiqv.fsf@yoom.home.cworth.org>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha1; protocol="application/pgp-signature"
Cc: David Bremner <bremner@debian.org>
Precedence: list

--=-=-=
Content-Transfer-Encoding: quoted-printable

On Sat, 25 Jun 2011 09:45:58 -0300, david@tethera.net wrote:
> Here is an updated version.

Thanks. I've committed this now, (waiting to be pushed until I fix my
build---the symbols stuff---so I can actually run "make test" again).

> I'm not sure the best way to do a test of
> the cleaning; maybe we should ship a MANIFEST file containing the
> output of git ls-files. I'm not sure how much churn this would cause
> in git.  Perhaps it could be treated like version, and generated from
> git if possible.

Definitely wouldn't want a generated file under revision control. It
would be possible to just run "git ls-files" if we're in a git
repository and skip the test otherwise. Or...

> In any case I guess this couldn't really be part of
> our regular test suite, because all the other tests would fail ;).

Heh, that would be a bad failure mode. :-)

The typical way to do this (as far as I understand) is as part of "make
distcheck". The idea there is to make a tar file; verify that the tar
file can be unpacked, configured, built, and installed; and then to
verify that "make distclean" returns the directory to the same state as
just after having unpacked the tar file.

I'm not really all that concerned about it though. We don't add/remove
files all that often, and it's generally not too bad of a failure mode
if "make clean" isn't perfect.

So if someone added testing for this, that would be fine, but it's not a
high priority for me.

=2DCarl

=2D-=20
carl.d.worth@intel.com

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk4KI5gACgkQ6JDdNq8qSWgTggCffKQMyprVvAEaVSM01vXZ/SQV
VzIAn2eO7IBwOU3DZ3UhimrpcRsEwdor
=P/8j
-----END PGP SIGNATURE-----
--=-=-=--