https://bugs.exim.org/show_bug.cgi?id=2956
John Jetmore <jj33@???> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jj33@???
--- Comment #9 from John Jetmore <jj33@???> ---
(In reply to Jeremy Harris from comment #8)
> (In reply to Andrew Aitchison from comment #7)
>
> > Also, do we know the name of the exim executable at make time ?
> > I think $(BIN_DIRECTORY) gives us the path, but Debian and Ubuntu change the
> > name to exim4.
>
> Sigh, good point. Maybe yet another build-config item, to handle such
> bloody-awkward distros (Exim version 3 was twenty years ago, dammit).
> But given the below, moot.
I perked up at this because I thought it was a perl question I could help with
but I now realize it's not. Apologies if I am addressing a different issue
than what is asked.
I think what you are saying is "exim_msgdate needs to call exim, which it
refers to as 'BIN_DIRECTORY/exim', with BIN_DIRECTORY getting replaced by the
build process. Therefore how does the build process handle distros that use a
different binary name than exim4"
Assuming I read that right, the correct answer is it's not the exim distro's
problem. There are already tools like this (see exiqgrep.src), and they are
handled by the packager who chooses to change the binary name, as is proper
(see
https://sources.debian.org/src/exim4/4.96-13/src/exiqgrep.src/ which
refers to BIN_DIRECTORY/exim4)
--
You are receiving this mail because:
You are on the CC list for the bug.
