FS#22744 - [exim] compile time options are being set by ugly sed hackery

Attached to Project: Community Packages
Opened by Moritz Wilhelmy (wzff) - Friday, 04 February 2011, 03:48 GMT
Last edited by Angel Velasquez (angvp) - Saturday, 07 May 2011, 19:20 GMT
Task Type General Gripe
Category Packages
Status Closed
Assigned To Angel Velasquez (angvp)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

The exim compile time options are being set by an ugly pipe-hackery of incremental sed commands, each modifying the output of the previous one. This is an ugly, unreadable hack and effectively prevents users from being able to read which options are actually applied and available. I suggest to include a modified copy of src/EDITME alongside with the PKGBUILD and copy it to Local/Makefile at the beginning of build() so the local sysadmin can make modifications to that file and recompile exim with compile-time-options which fit their needs. The EDITME file is supposed to be edited by whoever wants to change exim options.

Quoting src/EDITME:
This is the template for Exim's main build-time configuration file. It contains settings that are independent of any operating system. These are things that are mostly sysadmin choices. The items below are divided into those you must specify, those you probably want to specify, those you might often want to specify, and those that you almost never need to mention.

This would make it more convenient to rebuild exim with additional database backends, like for instance LOOKUP_PGSQL, without having to make the official exim package depend on something only a minority of the users use.
This task depends upon

Closed by  Angel Velasquez (angvp)
Saturday, 07 May 2011, 19:20 GMT
Reason for closing:  Implemented
Additional comments about closing:  added a exim.Makefile which isa copy of Local/Makefile

Loading...