Hello list,
Currently the build system for the extras (table, filters etc ...) is not
really intelligent.
It does not check is the required libs or interpreters in present on the
machine and doesn't even use the correct path for the libs.
This is a problem for user and packagers since now it's not possible to easily
provide an OpenSMTPD package with mysql for example.
After talking to gilles@ in private on IRC we tought on possibly make the
following changes :
1) Each extras will provides it's own configure script
2) Each configure scripts will correctly check its dependancies
3) All extras will be shipped in a single archive
4) Maybe have just one branch in the git since OpenBSD doesn't ship with smtpd
extras.
For 1, it will simply keep the configure as simple as it need to be
For 2, well ...
For 3, I know that the FreeBSD ports infrastructures can handle this correctly
(having multiple ports that depends on one distfiles, the Qt ports for plugins
does that). Is there some ports/packages infrastructure that can't ?
For 4, I think that for now smtpd uses ${PREFIX}/libexec/opensmtpd/ to look at
custom tables/filters which will fail on OpenBSD if the user use the smtpd in
base (PREFIX=/usr) and an extra via the packages (PREFIX=/usr/local IIRC).
Also currently the libasr doesn't provide an .pc for pkg-config and OpenSMTPD
doesn't check in configure if libasr is available, it simply fail when building.
Is it possible to provide a .pc and maybe tag a stable release for libasr so
packagers can start packaging in the different OS.
Let the discution begins.
Cheers.
--
Emmanuel Vadot <[email protected]>
--
You received this mail because you are subscribed to [email protected]
To unsubscribe, send a mail to: [email protected]
