On 27/7/2017 10:45 μμ, Peter wrote:
You don't have to actually rebuild the src.rpms, although you certainly
can if you want. There are binary rpms you can just install as per the
directions at:
http://ghettoforge.org/index.php/Postfix3
Yep, I know; As I've mentioned, I prefer to build against ltb openldap,
which has proved to be well-updated and trustworthy.
[Additionally, I like to maintain my (slight) rpm-build know-how; it has
been very useful in various occasions.]
[I must pay my respect to GhettoForge who are providing reliable updated
packages for numerous software projects.]
Interestingly, I've also noticed that postfix binaries are built against
original mysql, although CentOS 7 now uses mariadb as standard.
I've tried switching the dependency to mariadb instead, and building
using mariadb works fine as well.
Is there a particular reason why mysql is used in the spec file rather
than mariadb (both in the GhettoForge and in the Oostergo versions)?
The main thing to be concerned about here is the possibility of
different versions of the compiled berkley db files. Simply re-running
postmap on the source files should correct those issues.
I haven't noticed any such issues, but I'll keep an eye for possible
problems.
My concern was that by switching the whole directory I might have missed
some files that may have been needed, although I did not notice any such
files (by comparing the content of the /etc/postfix/ directories on the
two servers) when I tried to resolve the issue.
I am still wondering about the possible cause of the startup problem I
faced.
Cheers,
Nick
