Am 04.01.2013 05:06, schrieb Michael Elkins: > 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.
Thank you. >> --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: Oh, it does, albeit to a subdirectory below the build directory - that is one of the purposes: check if it "make install"/"make uninstall" unduly leaves residues... Just look at what the distcheck target is doing, and has been doing for every automake version that I remember (including 1.4), and possibly automake's NEWS file, there were changes to the naming of the install paths so this looks pretty intentional in spite of what you then quoted: > 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. It would seem this paragraph needs to be revised. > 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'. I know this is possible, but I have seen "make distcheck" failures when run without sudo due to chgrp failing.
