On Fri, Jan 04, 2013 at 02:41:01AM +0100, Matthias Andree wrote:
Am 04.01.2013 01:21, schrieb Mutt:
The chgrp and chmod are not due to the permissions on /usr/local, but
rather the configure script has detected that the default mail spool for
your system requires the dotlock binary to have elevated permissions.
You can either change the permissions on your default mail spool to world
writable, or use the --with-homespool option.
Would it be sensible to have this informational text added to the
install-hook, for users to know why it fails?
changeset: 6283:90f7869decec
branch: HEAD
tag: tip
user: Michael Elkins <[email protected]>
date: Fri Jan 04 04:05:06 2013 +0000
summary: When "make install" fails to chgrp or chmod the mutt_dotlock
binary, add the reason why we are doing this so the user knows what to look for.
--with-homespool would also be a helpful addition to the "distcheck"
mode, possibly through adding
AM_DISTCHECK_CONFIGURE_FLAGS=--with-homespool to the Makefile.am.
What would be the advantage? Make distcheck doesn't seem to perform the
install step:
Automake also generates a `distcheck' rule that can be of help to
ensure that a given distribution will actually work. `distcheck' makes
a distribution, then tries to do a `VPATH' build (*note VPATH
Builds::), run the test suite, and finally make another tarball to
ensure the distribution is self-contained.
If you need it for some reason:
The user can still extend or override the flags
provided there by defining the `DISTCHECK_CONFIGURE_FLAGS' variable, on
the command line when invoking `make'.
