On Wednesday, December 07, 2016 12:50:05 AM Viktor Dukhovni wrote:
> > On Dec 7, 2016, at 12:34 AM, Scott Kitterman <post...@kitterman.com>
wrote:
> >> Instead of partly disabling DANE support, it seems to make more
> >> sense to switch to unbound or BIND.
> >
> > I agree. I think most users don't understand the distinction between the
> > parts of the archive.
>
> Let's hope the word gets out somehow. In the meantime, are you still
> involved in packaging Postfix for Debian? I am still hoping to some
> day see a Postfix package with a correct "postfix-files" file (that
> does not list files the package does not include) and does not leave
> out the makedefs.out file that shows the build settings...
>
> With a broken "postfix-files" none of the multi-instance features work.
> It should be possible to create secondary instances on Debian via
> "postmulti -e create -I postfix-mumble" and "postfix check" should
> not fail for lack of files to match the content of "postfix-files".
>
> I was hoping this would be fixed with the 3.1 packages in stretch,
> but no luck so far.
As I recall from our previous discussions on the topic (and what I read in the
documentation), since we split the various dynamic map types into their own
binary packages, we need to make sure that the basic postfix package doesn't
reference those files and that the binary includes a postfix-files snippet to
drop in a postfix-files.d directory. Is that right?
As an example, for mysql (the html docs are in a doc pacakge):
$shlib_directory/${LIB_PREFIX}mysql${LIB_SUFFIX}:f:root:-:755
$manpage_directory/man5/mysql_table.5:f:root:-:644
is what goes in /etc/postfix/postfix-files.d/mysql (for lack of a better name)
Is there an upstream method to split those lines out into separate files based
on the build type? I can come up with something Debian specific to do it, but
if it's already covered, I don't want to re-invent the wheel.
Scott K
