Folks,
It looks like none of the Exim maintainers are still using Solaris. I'm
going to use Solaris in this email, but roughly everything which applies
to it also applies to every non-Linux non-BSD system.
We're all on various Linux or BSD systems. We do not have any Unix
variants other than BSDs and Linux distributions in our automatic build
farm: <
http://eximbuild.mrball.net/cgi-bin/show_status.pl>
Exim 4.83 does not build cleanly on Solaris, because we're using
`timegm()`; see: <
http://bugs.exim.org/show_bug.cgi?id=1526>
The Linux man-page for timegm documents a workaround approach, but none
of the devs can test it. We could install some modern open-foo variant
of whatever forks of Solaris happened (Indiana stuff? I used to know
these details) but that just solves the problem as a once off, it does
not solve testing repeatedly and discovering issues before a release.
So, can anyone out there help?
We're looking for:
(1) Someone who can hack C on Solaris and/or other non-Linux non-BSD
and who is willing to work on helping maintain Exim on such
platforms
(2) Some build agents; see various pages at
<http://eximbuild.mrball.net/> for requirements. Because so much
of what Exim does involves root transitions, this is something for
either a VPS / throw-away OS instance, or for running inside a Zone
if you trust the Zone isolation.
Basically, you set up an account on a box (inside a restricted Zone
is just fine) and give it a cronjob which runs the build agent,
which pulls from Git, tries to compile, tries to run tests. So
there's arbitrary code execution by anyone who can push to the Exim
repositories, and the sudo to root within the running environment
needs some isolation.
Not something to run on a production instance ;-) but for someone
who already runs a bunch of Solaris VMs and can easily run another,
or who uses Zones, it's a way to help make sure that Exim will
continue to work on your OS in the future.
Thanks,
-Phil
