Quanah Gibson-Mount wrote:
We currently use postfix as a part of our overall product, which means
that it ends up being packaged inside our own RPM (or deb, etc)
packages, and then redeployed when our product is installed. One thing
I've noticed about the postfix build system in this is that it assumes
you are building postfix specifically to be run on the box you're
building it on, which in what we are doing is not really the case.
As a part of all this, we also allow people to check out and build the
FOSS edition of our product. To make it easier on those who want to do
this, I'm trying to make it so they can build postfix as whatever user
they want, since our own install process takes care of setting up
permission, etc, for postfix. However, the postfix-install script
doesn't seem to have a concept of this, which makes it somewhat
annoying to use, as I have to essentially patch around it. Of the
numerous software applications we build as the underlying components
to our product, Postfix is the only one that goes to such pains. Is
there a way that I'm missing to turn off this behavior in
postfix-install besides patching it to turn off its checks?
Have you considered allowing the use of an existing instance of Postfix?
Many people tend to not consider packages that require and ship with
their own versions of externally maintained packages.
Terry
