Am 04.01.2013 15:45, schrieb Michael Elkins: > On Fri, Jan 04, 2013 at 09:35:37AM +0100, Matthias Andree wrote: >> 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... > > Thanks, I didn't read the entire section, and I see it does mention it > near the bottom of that section. > > Here is what is generated in the Makefile: > > && ../configure --srcdir=.. --prefix="$$dc_install_base" \ > $(AM_DISTCHECK_CONFIGURE_FLAGS) \ > $(DISTCHECK_CONFIGURE_FLAGS) \ > > The problem I see with hardcoding AM_DISTCHECK_CONFIGURE_FLAGS with any > particular option is that since it is not possible to override that > option, any other developer trying to use this functionality to test > builds with a different feature set is stuck. This is similar to the > sitatuion where the user of the configure script must specify > non-default options for their situation.
If you cannot override --with-homespool by adding a later --without-homespool or --with-homespool=no option on the command-line, then that is a configure.ac issue that can be fixed. It's in the autoconf.info documentation, under "External Software", and if you want, I can send a patch later (probably on Sunday). > If you are seeing install failures when the chmod/chgrp is not required, > please file a bug and I will look into that. It is required on my system¹, yet an unprivileged user should not see "make distcheck" failures due to that. ¹ drwxrwsr-x 2 root mail 4096 Dez 23 18:07 /var/spool/mail/
