Re: chroot warnings for postfix-script, invitation for testing (was: I swear the file is there...)

From: (no name) (no email)
Date: Thu Jun 26 2003 - 12:35:02 EDT


On Thu, 26 Jun 2003, Matthias Andree wrote:

> On Thu, 26 Jun 2003, wrote:
>
> > On Mon, 23 Jun 2003, Matthias Andree wrote:
> >
> > > Most of the patch is a rename of conf/postfix-script to
> > > conf/postfix-script.in, that makes it big (approx 550 lines) so I don't
> > > mail it. diff/patch could really use an option to track file renames...
> > >
> >
> > Thanks for this contribution.
> >
> > Why is it necessary to rename postfix-script? It is perhaps more
> > appropriate to use a second script (or script template). The second script
> > can be invoked from the main postfix-script.
>
> The issue here is to get the $AWK variable from makedefs and use it from
> postfix-script.
>

Why is this necessary? What Unix systems don't have a v7 compatible
/bin/awk? My makedefs.out has "AWK = awk", this does not justify
generating postfix-script on the fly. The AWK in makedefs.out records what
was used on the *build* machine to construct the software, it should not
be taken as a reliable indication of what to run on the *target* machine.

Do not confuse the build and install environments. If awk needed to be
configurable in Postfix, we would have a main.cf "awk_path" parameter.

-- 
	Viktor.







Hosted Email Solutions

Invaluement Anti-Spam DNSBLs



Powered By FreeBSD   Powered By FreeBSD