Bug#783813: exim4-daemon-custom could not be build from source

[Marko von Oppen]

Hi,

after waiting 3 years for a fix and running inbetween oldoldstable 
version of Exim4 I managed today building a new exim4-daemon-custom 
package from current stable source package.

There are two steps necessary to build custom packages:
1) uncomment custom packages in debian/control
2) in file debian/rules copy the line
    'cp EDITME.eximon $(<D)/Local/eximon.conf'
    from rule 'b-exim4-daemon-light/build-$(buildname)/exim: 
b-exim4-daemon-light/Makefile configure-stamp'
    to rule 'b-exim4-daemon-custom/build-$(buildname)/exim: 
b-exim4-daemon-custom/Makefile configure-stamp'

I included a full patch of my changes to 'debian' directory.

I do not know the whole Debian package build process. It seems not so 
relevant what in the 'extradaemonpackages=' line is specified. It seems 
that all packages from debian/control files are built. Even if I remove 
the 'exim-daemon-heavy' from 'extradaemonpackages=' line, the 'heavy' 
packages are built anyway. I suppose this is the reason why the 'custom' 
packages are commented out there.

So I suggest the following solution for the problem:
1) Let the custom packages in debian/control commented out but add a 
comment in debian/rules that these lines have to be commented out to 
build 'custom' packages.
2) Add the line mentioned above to debian/rules.

Finally I suppose that the mechanism using 
'debian/create-custom-package' to create additional packages not named 
'-custom' will not work anymore. There are now hardcoded rules for 
custom packages inside debian/rules.

BR
Marko
-------------- next part --------------
A non-text attachment was scrubbed...
Name: exim4_custom_build.patch
Type: text/x-diff
Size: 10054 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-exim4-maintainers/attachments/20170907/35a04e16/attachment.patch>