From 21b7ceb9df612f7573b6c40fb545ab75d706690a Mon Sep 17 00:00:00 2001 From: Dave Love Date: Sat, 3 May 2003 14:40:25 +0000 Subject: [PATCH] (MAIL_USE_FLOCK): Don't define if we should use maillock. --- src/s/gnu-linux.h | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/src/s/gnu-linux.h b/src/s/gnu-linux.h index 60dd66a9fa5..8782c189a64 100644 --- a/src/s/gnu-linux.h +++ b/src/s/gnu-linux.h @@ -129,8 +129,18 @@ Boston, MA 02111-1307, USA. */ /* On GNU/Linux systems, both methods are used by various mail programs. I assume that most people are using newer mailers that have heard of flock. Change this if you need to. */ - +/* Debian contains a patch which says: ``On Debian/GNU/Linux systems, + configure gets the right answers, and that means *NOT* using flock. + Using flock is guaranteed to be the wrong thing. See Debian Policy + for details.'' and then uses `#ifdef DEBIAN'. Unfortunately the + Debian maintainer hasn't provided a clean fix for Emacs. + movemail.c will use `maillock' when MAILDIR, HAVE_LIBMAIL and + HAVE_MAILLOCK_H are defined, so the following appears to be the + correct logic. (MAILDIR is defined in maillock.h.) -- fx */ + +#if !(defined (HAVE_LIBMAIL) && defined (HAVE_MAILLOCK_H)) #define MAIL_USE_FLOCK +#endif /* Define CLASH_DETECTION if you want lock files to be written so that Emacs can tell instantly when you try to modify -- 2.39.5