ports/69128: [work-around] mail/postfix configure glitch in adding multiple items to POSTFIX_OPTIONS in BATCH mode

[Paul Seniura]

>Number:         69128
>Category:       ports
>Synopsis:       [work-around] mail/postfix configure glitch in adding multiple items to POSTFIX_OPTIONS in BATCH mode
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Jul 15 21:00:42 GMT 2004
>Closed-Date:
>Last-Modified:
>Originator:     "Paul Seniura" <pdseniura at techie.com>
>Release:        FreeBSD 5.2-CURRENT i386
>Organization:
State of Okla. D.O.T.
>Environment:
System: FreeBSD techpc04.okladot.state.ok.us 5.2-CURRENT FreeBSD 5.2-CURRENT #1: Thu Jul 15 10:22:35 CDT 2004 root at techpc04.okladot.state.ok.us:/usr/obj/src/sys/IBM300SY_4BSD_Os i386


>Description:


Hi,


I couldn't find any references to this sort of problem via
Google & GNATS etc.  I found a work-around, tho, so it may
be worthy of a PR just so to not lose track of it.  ;)


I'm seeing a problem when adding more than one item to
POSTFIX_OPTIONS in BATCH mode.  According to the comments
in the port's FreeBSD Makefile (not the original project),
we are suppose to separate multiple options with a simple
space/blank character.  This causes the following error
when building the app.

Relevent items in my /etc/make.conf:

[...]
BATCH=yes
[...]
POSTFIX_OPTIONS="OpenLDAP Test IPv6"
POSTFIX_DEFAULT_MTA=yes
[...]


My portupgrade log of mail/postfix as of latest CTM buckets
from last night using the above settings:

[...]
** No need to upgrade 'linuxpluginwrapper-20040310_2' (>= linuxpluginwrapper-20040310_2). (specify -f to force)
--->  Upgrade of mail/postfix started at: Thu, 15 Jul 2004 12:11:18 -0500
--->  Upgrading 'postfix-2.1.3,1' to 'postfix-2.1.4,1' (mail/postfix)
--->  Build of mail/postfix started at: Thu, 15 Jul 2004 12:11:18 -0500
--->  Building '/usr/ports/mail/postfix'
===>  Vulnerability check disabled, database not found
env: Test: No such file or directory
*** Error code 127

Stop in /src/ports/mail/postfix.
** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade19267.8 make
** Fix the problem and try again.
--->  Build of mail/postfix ended at: Thu, 15 Jul 2004 12:11:20 -0500 (consumed 00:00:01)
--->  Upgrade of mail/postfix ended at: Thu, 15 Jul 2004 12:11:20 -0500 (consumed 00:00:01)
** No need to upgrade 'XFree86-Server-4.3.0_14' (>= XFree86-Server-4.3.0_14). (specify -f to force)
[...]


I've tried all kinds of single- & double-quotemarks,
escaping them, etc., and got various errors ranging from
what is shown above, to "Unterminated quoted string",
among others.

The various portupgrade tools are up-to-date, too, here.


>How-To-Repeat:


Try adding more than one option to POSTFIX_OPTIONS in your
/etc/make.conf, using plain blanks as per documentation,
set BATCH=YES there, then build either mail/postfix or
mail/postfix-current as needed.


>Fix:

What I did to _finally_ fix this for good was to change the
line in /etc/make.conf to quote and escape the blanks thusly:

POSTFIX_OPTIONS="OpenLDAP\ Test\ IPv6"

The recent postfix versions will build & install all three
options now.  :)


As an aside, I see similar build problems with net-snmp
and trying to hard-code some MIB strings for it in
/etc/make.conf, too, but escaping the blanks didn't fix
them and neither did single-/double-quotemark tricks. 
SNMP will allow underscores '_' in those MIB strings,
tho, whereas mail/postfix will not, of course.


So I am not sure who/what/where this problem resides. 
It's the age-old problem of "how much how many how deep
must my quote- and escape-marks be seen".  ;)  
I'll log this work-around for postfix, tho.  It might help
the PRs w/r/t sysinstall'ing postfix, too, maybe?


  --  thx, Paul Seniura
           System Specialist
           State of Okla. D.O.T.


>Release-Note:
>Audit-Trail:
>Unformatted: