https://bugs.exim.org/show_bug.cgi?id=2956
--- Comment #8 from Jeremy Harris <jgh146exb@???> ---
(In reply to Andrew Aitchison from comment #7)
> > It's using a hardwired config file path, at least in the testsuite.
> > Noticing the -C the testharness gave it would be good;
>
> I've got that working, which confuses me. I had expected that to pass one of
> the configs in test/confs/
It does; the one you supplied as confs/0700 - but the code picks up
the -C option and ignores it.
The hardcoded file is just after a commented-out "die".
>
> > but for production use - how about using `exim -bP localhost_number'
> > as a default for no "-C foo" given?
>
> That makes some sense, but exim_msgtime has perl taint set, so I cannot
> easily run a binary by name given as an argument.
I was assuming exim in $PATH - but I don't know how perl taint restricts
that.
> 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.
> It isn't working in attachment 1435 [details], but after a bug-fix, the
> build now correctly writes the configfile list into the script and I can
> search that for localhost_number.
That'll be fine apart from the testsuite, which needs the -C value to
take precedence.
--
You are receiving this mail because:
You are on the CC list for the bug.
