It seems to me that the package tries to subvert policy 10.7.4 here.  Other
bugs have been opened against this source package in the past (for example
#414469, #402432, #414484).  I think that trying to get around policy by having
the postinst do stuff like this:

echo "************************************************************************"
echo "* Warning! DTC setup is not completed. The postinst didn't do it all.  *"
echo "To finish the installation: execute /usr/share/dtc/admin/install/install"
echo "************************************************************************"

And thus telling the user to run a script which modifies the configuration
files of a dozen other packages without warning, and often without a way back,
is violating the spirit of the policy.

stew

The goal of my software is to handle the configuration of the server. If
we follow what you are saying, then an administrator would have to spend
hours to setup his server manually for a single installation. Do you
think that this is manageable?

Note also that I've opened discussions about it, and that I'm trying to
solve the issue, but the postfix maintainer (for example) didn't even
bother to reply. Upstream said that a conf.d folder isn't even possible.
What solution do I have here?

Thomas

When I'm at it, I just ran wc -l on the output of the script. It's
exactly 200 lines long. How can you claim that this is "without
warning"? The script is telling quite verbosely what it's doing!

Thomas

I don't care.  This isn't a reason for your package to ignore debian
policy.

The solution is to not modify the cofiguration files of other packages,
obviously.


"My package doesn't at all fit with debian policy.  My package cannot be
made to follow policy" isn't a sign that the policy needs to be changed
or that the policies should be ignored.  It is a sign that the package
doesn't belong in debian.

stew