unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: MAIL_USE_FLOCK and Debian.
Date: Mon, 17 Feb 2003 02:20:26 -0500	[thread overview]
Message-ID: <E18kfZi-0007eI-00@fencepost.gnu.org> (raw)
In-Reply-To: <87znoxi93a.fsf@raven.i.defaultvalue.org> (message from Rob Browning on Sat, 15 Feb 2003 14:26:33 -0600)

    If I understand the situation correctly, I'm not sure this is anything
    that actually can be decided automatically.  The problem is that in
    the final analysis, the policies with respect to locking may come down
    to a local administrative decision.

I think that is even more reason to control the decision at run time.
Binaries are often moved from machine to machine, on a given platform.
People will, for instance, install the Debian Emacs package on various
Debian systems, some of which use liblockfile and some of which don't.

A run-time configuration option is much more powerful and convenient.

So the code should compile support for using liblockfile whenever
liblockfile is defined, and should compile the other method as well
(whichever other method is used now), and the final choice would be
controlled by an environment variable or a file installed with Emacs.

It would be ok to extend this idea of run-time choice to the question
of whether to use flock.  The idea would be that there are three
possible methods, and the code for each one would be compiled whenever
the platform permits that, and the final choice would be made at run
time.

The variable MAIL_USE_FLOCK would then help control the default
setting for the run-time choice.


Do you agree?  Would you like to implement it?

  reply	other threads:[~2003-02-17  7:20 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-15  7:02 MAIL_USE_FLOCK and Debian Rob Browning
2003-02-15 19:11 ` Richard Stallman
2003-02-15 20:26   ` Rob Browning
2003-02-17  7:20     ` Richard Stallman [this message]
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=E18kfZi-0007eI-00@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.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).