From: Rob Browning <rlb@defaultvalue.org>
Subject: MAIL_USE_FLOCK and Debian.
Date: Sat, 15 Feb 2003 01:02:11 -0600 [thread overview]
Message-ID: <87lm0ijabw.fsf@raven.i.defaultvalue.org> (raw)
On a Debian system, the setting of MAIL_USE_FLOCK in s/gnu-linux.h is
guaranteed to be wrong, so right now, Debian applies the patch below
and adds -DDEBIAN to CFLAGS in debian/rules. Of course this fix isn't
appropriately general because it only works for people using
debian/rules to build Emacs packages. So I'd like to figure out what
the "right" way to fix it would be. The general rule is that on a
Debian system, you should only use liblockfile, nothing else.
Though I have patches that make sure that liblockfile is used and that
the location of the mail spool is detected correctly, we still need an
acceptable way to make sure that on a Debian system, MAIL_USE_FLOCK
isn't defined.
My patches also add support for dynamic detection and use of
USE_MAIL_SPOOL_DIRECTORY, CONF_MAIL_SPOOL_DIRECTORY,
CONF_MAIL_PROGRAM_NAME, MOVEMAIL_LOCK_LIBS, and the elisp-side
mail-spool-directory variable, though I'm not sure those changes, as
they stand, will necessarily be wanted upstream. I discussed them
with Gerd some time back, but now I need to finish re-evaluating them
against current CVS, and to discuss them here to make sure they're
still desired.
Thanks
--- emacs21-21.2.orig/src/s/gnu-linux.h
+++ emacs21-21.2/src/s/gnu-linux.h
@@ -130,7 +130,14 @@
programs. I assume that most people are using newer mailers that
have heard of flock. Change this if you need to. */
-#define MAIL_USE_FLOCK
+/* 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. */
+#ifdef DEBIAN
+# undef MAIL_USE_FLOCK
+#else
+# define MAIL_USE_FLOCK
+#endif
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
next reply other threads:[~2003-02-15 7:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-15 7:02 Rob Browning [this message]
2003-02-15 19:11 ` MAIL_USE_FLOCK and Debian Richard Stallman
2003-02-15 20:26 ` Rob Browning
2003-02-17 7:20 ` Richard Stallman
2003-02-17 15:31 ` Rob Browning
2003-02-17 21:20 ` Florian Weimer
2003-02-17 21:32 ` Rob Browning
2003-02-17 21:41 ` Florian Weimer
2003-02-17 21:56 ` Alan Shutko
2003-02-17 22:20 ` Rob Browning
2003-02-18 16:03 ` Rob Browning
2003-02-18 13:59 ` Richard Stallman
2003-02-18 15:58 ` Rob Browning
2003-02-19 7:16 ` Richard Stallman
2003-02-19 17:11 ` Rob Browning
2003-02-19 18:03 ` David Masterson
2003-02-20 18:21 ` Richard Stallman
2003-02-20 19:22 ` Rob Browning
2003-02-21 21:44 ` Richard Stallman
2003-02-24 2:58 ` Rob Browning
2003-02-28 8:14 ` Michael Sperber [Mr. Preprocessor]
2003-03-01 21:44 ` Richard Stallman
2003-03-02 10:06 ` Michael Sperber [Mr. Preprocessor]
2003-03-03 18:58 ` Richard Stallman
2003-03-04 8:30 ` Michael Sperber [Mr. Preprocessor]
2003-03-05 20:46 ` Richard Stallman
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lm0ijabw.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.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://git.savannah.gnu.org/cgit/emacs.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).