On Sun, 16 Jan 2005 [EMAIL PROTECTED] wrote:
> Hi,
Hello
> the upgrade vom debian 8.12 to 8.13 was breaking our
> sendmail configuration which was working well for years.
It doesn't sound like it broke your setup - just that you
can't take advantage of some of the features (like Makefile)
> The reason is that programs like
> /usr/share/sendmail/update_mk
> try to analyze the m4 structures to build a list of
> included files and configuration files to update
> /etc/mail/databases and /etc/mail/Makefile
True, that is exactly how things run
> We do use our own m4 configuration extensions, which
> have statements like
> include(CONFIGDIR/something.m4) or
> define(`confCT_FILE', DBDIR/sendmail.ct)
>
> where CONFIGDIR and DBDIR are M4-macros defined elsewhere.
>
> This was working pretty well with sendmail for years, and
> it is still working, since it is allowed to use any
> m4 macro function.
>
> Unfortunately, the debian scripts don't evalute the
> m4 macros, but simply look for includes and definitions,
> and thus write CONFIGDIR/something.m4 and DBDIR/sendmail.ct
> without macroexpansion in the Makefile and /etc/mail/databases.
> This is a bug.
That is debatable... again, this prevents you from using some of
the features provided for the simpler installations, but doesn't
really impact your full use of m4 to manage sendmail.
> The correct way would be to run the configuration through m4
> and trace it to find the included files and take the configuration
> file paths from the final output (or .cf file).
That would be an improvement - but I refuse to use the .cf file,
and for good reasons... amongst them, the next big sendmail update
(sendmail-X) will not use the same sendmail.cf - at this point it
isn't even clear if sendmail.mc will be used (but likely not).
I'd gladly take patches (full, or partial) to improve my support of
sendmail.mc :)
--
Rick Nelson
All the existing 2.0.x kernels are to buggy for 2.1.x to be the
main goal.
-- Alan Cox
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
