[HEADS UP] movemail locking overhaul ahead

ms> The locking policies can be controlled through three ms> mechanisms (by descending precedence): ms> - Specification on the movemail command line. ms> - Specification of an environment variable EMACSLOCKMETHOD ms> with the same possible values as the --mail-locking argument ms> to configure. ms> - Configuration via autoconf and src/config.h. Obviously XEmacs shouldn't be allowed to specify locking methods not implemented on the system in question. How do you plan to handle that given the precedence specified above? Or is this not a problem? Maybe XEmacs should bitch on startup (disabled through a site-start facility) if the environment variable or the 'mail-lock-variable is set to something strange for the system. We've already had one incident where somebody made a RedHat package using flock when all of the Linux MTAs use file locking. I don't know how this would be implemented, though :-( -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 __________________________________________________________________________ __________________________________________________________________________ What are those two straight lines for? "Free software rules."