Re: MAIL_USE_FLOCK and Debian.

[Rob Browning <rlb@defaultvalue.org>]

Richard Stallman <rms@gnu.org> writes:

>     However, if movemail only needs (and allows) two strategies normally,
>     and if adding support for liblockfile to that set then covers all the
>     relevant cases, then we should be OK.
>
> I think so.

It looks like the two existing movemail strategies are
MAIL_USE_SYSTEM_LOCK and MAIL_USE_MAILLOCK.  Presuming that's correct,
then we have to decide how to handle liblockfile.

In addition to the thread-safe, lower-level locking functions like
lockfile_create, liblockfile also provides maillock and touchlock
convenience functions, so if we're on a system that has both libmail
and liblockfile, which do we choose?  Unless we were going to do
something like runtime dynamic linking, we'll have to link against one
lib or the other at build time.  I don't really have any idea how
often this might be an issue.  The way the code is arranged in Debian,
liblockfile is always preferred if found...

-- 
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