Re: [MaraDNS list] not fixed upstream after all

> I don't think include functionality in deadwood addresses the user's
> issue since he clearly needs it in the authoritative server. In any case
> the "execfile" documentation is quite hard to follow.

I will add more documentation for "execfile" in Deadwood over the next
few days.  It's been really hectic the last week; I had one job
interview Friday and am flying out today for another interview
tomorrow.  I should be able to make time to document "execfile" better
this weekend.

In terms of adding "execfile" support to the authoritative server, my
answer before I began accepting donations was "No, because UNIX [1]
already has a program called 'bash' that can do this.  'man bash' for
details." or "No, because MaraDNS has the /read directive that can do
this for zone files.".  Now that MaraDNS' continued development and
support is user-funded, the answer is "No, because I currently don't
have enough funding to implement new features."  (Note: I do manage to
get a job offer, I may no longer be able to implement new MaraDNS
features for reasonable sums of money.  I will let the list know when
this happens).

> This need not necessarily be an upstream issue. If your processing
> can handle running dpkg-reconfigure after updating the include file,
> then this could be accomplished with debconf.

UNIX has a program called 'bash' that can combine multiple files in to
a single file.  'man bash' for details.  :)

- Sam

[1] I understand that POSIX does not require that Bash be included
with a UNIX system.  However, I can not think of a recent
implementation of UNIX that doesn't come with BASH (AIX and HP-UX are
legacy implementations, not recent implementations.  I *believe*
Solaris comes with Bash these days; I *know* most Linux distros, BSD,
and Mac OS X do come with Bash).  If you want to be pedantic about it,
just do a s/bash/sh/ig while reading this email.