On Thu, Feb 12, 2015 at 04:29:37PM +0100, li...@rhsoft.net wrote:
> >The only difference between "install" and "upgrade" is that one is
> >interactive and the other is not. That is, "install" is an upgrade
> >from zero with all the answers pre-determined
>
> "make install -non-interactive" simply ends in *nothing* installed into the
> build-tree nor somewhere else
The "-non-interactive" option is "postfix-install" command-line argument, it
is NOT a make argument. The Postfix Makefile contains the following relevant
targets:
install: update
$(SHLIB_ENV) shlib_directory=$(SHLIB_DIR_OVERRIDE) $(SHELL) \
postfix-install
package: update
$(SHLIB_ENV) shlib_directory=$(SHLIB_DIR_OVERRIDE) $(SHELL) \
postfix-install -package
upgrade: update
$(SHLIB_ENV) shlib_directory=$(SHLIB_DIR_OVERRIDE) $(SHELL) \
postfix-install -non-interactive
non-interactive-package: update
$(SHLIB_ENV) shlib_directory=$(SHLIB_DIR_OVERRIDE) $(SHELL) \
postfix-install -non-interactive -package
For non-interactive building of packages use:
http://www.postfix.org/PACKAGE_README.html
If you want to fully automate this process, specify all
the non-default installation parameters on the command
line:
% make non-interactive-package install_root=/some/where...
With Postfix versions before 2.2 you must invoke the
post-install script directly (% sh post-install -non-interactive
install_root...).
With Postfix 3.0 and later, the command "make package
name=value
..." will replace the string MAIL_VERSION in a configuration
parameter value with the Postfix release version. Do not
try to specify something like $mail_version on this command
line. This produces inconsistent results with different
versions of the make(1) command.
This was even updated for 3.0.
--
Viktor.
