Update Doc for recent linux distros

diff --git a/BuildingDocs.md b/BuildingDocs.md
index e25a966df72dbbdd39070380cff2aafbca3697a5..b21fb41f2cd7786558fedf7f37c1761b7df79fa9 100644 (file)
--- a/BuildingDocs.md
+++ b/BuildingDocs.md
@@ -1,15 +1,22 @@
 Running the stage which builds docs helps to test our txt, pdf, and html generation across the various versions of ghostscript and xml support that exist through all participants in the Exim BuildFarm.  It requires quite a few packages to be installed.  I'll relate my experiences getting it working on CentOS systems and hopefully this can be enough of a guide to get it working on yours.
 
 ## Getting Required Packages
 Running the stage which builds docs helps to test our txt, pdf, and html generation across the various versions of ghostscript and xml support that exist through all participants in the Exim BuildFarm.  It requires quite a few packages to be installed.  I'll relate my experiences getting it working on CentOS systems and hopefully this can be enough of a guide to get it working on yours.
 
 ## Getting Required Packages

-1. I had to find, download, and install the xfpt (Xml From Plain Text) rpm.  For CentOS 6, it installed with no problem.  For CentOS 5, I had to get the src rpm and rebuild it on my CentOS 5 build system.
-`rpm -Uvh xfpt-0.08-1.x86_64.rpm`
-The above package is available for download for [CentOS 6](http://www.blafasel.at/exim/doc_rpms/) and [CentOS 5](http://downloads.mrball.net/Linux/CentOS/5/RPMS/x86_64/). The package is available directly on Debian and Ubuntu distros.
+1. I had to find, download, and install the xfpt (Xml From Plain Text) rpm.
+The package is available directly on Debian and Ubuntu distros.
+For CentOS 6, it installed with no problem.
+For CentOS 5, I had to get the src rpm and rebuild it on my CentOS 5 build system: `rpm -Uvh xfpt-0.08-1.x86_64.rpm`
+The above package is available for download for [CentOS 6](http://www.blafasel.at/exim/doc_rpms/) and [CentOS 5](http://downloads.mrball.net/Linux/CentOS/5/RPMS/x86_64/).
+Fedora 27 does not seem to have it.
+There are git source repos on [github](https://github.com/nigelm/xfpt) and also [here](https://gitlab.quatermass.co.uk/mirrors/xfpt).

 2. I had to install several additional distro provided packages:
 `yum install xmlto ghostscript docbook-style-xsl gc w3m`
 2. I had to install several additional distro provided packages:
 `yum install xmlto ghostscript docbook-style-xsl gc w3m`

-3. I had to find, download, and compile the sdop tarball (Google found it on the debian build system).  For CentOS 6, it was as simple as:
+3. I had to find, download, and compile the sdop tarball (Google found it on the debian build system).
+There is a git copy of that [here](https://gitlab.quatermass.co.uk/jgh/sdop).
+For CentOS 6, it was as simple as:

 `./configure && make && make install`
 For CentOS 5, it was more complicated because the older version of gcc didn't like the way things were being typedef'd in the png headers; I had to do:
 `./configure --disable-jpeg --disable-png && make && make install`
 `./configure && make && make install`
 For CentOS 5, it was more complicated because the older version of gcc didn't like the way things were being typedef'd in the png headers; I had to do:
 `./configure --disable-jpeg --disable-png && make && make install`

-A package is available for download for [CentOS 6](http://www.blafasel.at/exim/doc_rpms/).  The package is available directly on the Debian and Ubuntu distros.
+A package is available for download for [CentOS 6](http://www.blafasel.at/exim/doc_rpms/).
+The package is available directly on the Debian and Ubuntu distros.

 
 

-Once that was in place, the build system can do all the steps to make all of the documentation.
\ No newline at end of file
+Once that was in place, the build system can do all the steps to make all of the documentation.

diff --git a/Installation.md b/Installation.md
index 472050bc56f4da93f2bde4b218637828ce102598..471d6d135235616c06e094f425b57544bfa7fc9e 100644 (file)
--- a/Installation.md
+++ b/Installation.md
@@ -7,10 +7,20 @@ If you want to run more than one instance of the build farm to test multiple dif
 
 ## Install Steps
 1. Make sure that all required packages for Exim to build successfully are installed. The minimal package requirements are the basic suite of compiler tools and basic libraries.  You will also need to install the ccache package.
 
 ## Install Steps
 1. Make sure that all required packages for Exim to build successfully are installed. The minimal package requirements are the basic suite of compiler tools and basic libraries.  You will also need to install the ccache package.

+A set needed for basic build (not including the buildfarm!) of a bulky-configuration Exim on Fedora 27 is:
+git gcc make
+pcre-devel
+libdb-devel libXaw-devel libXt-devel libidn2-devel libidn-devel
+lmdb-devel sqlite-devel hiredis-devel postgresql-devel mysql-devel
+openssl-devel openldap-devel
+perl-ExtUtils-Embed perl-experimental
+redhat-rpm-config

 
 2. Create the master exim user (i.e. the user that Exim changes uid to when it runs in normal operation).  I suggest the user **exim**.  If you already have the Exim package provided by your distro installed, chances are good that you already have a user named **exim**, **exim4**, or **Debian-exim**.  That user is fine.  This howto also assumes you use the groupname **exim**.
 
 
 2. Create the master exim user (i.e. the user that Exim changes uid to when it runs in normal operation).  I suggest the user **exim**.  If you already have the Exim package provided by your distro installed, chances are good that you already have a user named **exim**, **exim4**, or **Debian-exim**.  That user is fine.  This howto also assumes you use the groupname **exim**.
 

-3. Create a user that will run the Build Farm.  I suggest the user **farm**.  Due to some assumptions that are made in the test suite, the group name must also be **farm**. It is ok if you make it a secondary group or the primary group.  You also must assign a geckos name, or some tests will fail.  I suggest "Exim BuildFarm".  An example command that should work for most distributions:
+3. Create a user that will run the Build Farm.  I suggest the user **farm**.
+It can be your normal login, but be warned: you'll be giving it passwordless "sudo" permissions.
+Due to some assumptions that are made in the test suite, the group name must also be **farm**. It is ok if you make it a secondary group or the primary group.  You also must assign a GeCos name, or some tests will fail.  I suggest "Exim BuildFarm".  An example command that should work for most distributions:

 `useradd -m -c 'Exim BuildFarm' farm`
 
 4. Add **exim** as a secondary group to the **farm** user.  (You should **NOT** add **farm** as a secondary group to the exim user; this will cause test errors.)  Here is a sample user/group configuration:
 `useradd -m -c 'Exim BuildFarm' farm`
 
 4. Add **exim** as a secondary group to the **farm** user.  (You should **NOT** add **farm** as a secondary group to the exim user; this will cause test errors.)  Here is a sample user/group configuration: