Quanah Gibson-Mount:
> 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.
The Postfix build procedure assumes that the build machine is
representative for the environment where the software will be used.
For example, it builds FreeBSD binaries on FreeBSD not on Solaris.
> 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.
The postfix build and install procedures have documented processes
to set up file locations, as well file and directory permissions
and ownerships.
If the documented processes are inadequate, then perhaps you could
share specific information. Postfix is a more complex system than
the average UNIX app, and I am notoriously bad at guessing people's
thoughts.
Wietse
