Hi, pigeonhole/sieve check against dovecot's version comparing to what they have been built against. This means that whenever there is a minor version of dovecot released pigeonhole/sieve need to be rebuilt and then redistributed to users even if there is no need for it (I'm thinking of packaged versions of dovecot and dovecot-pigeonhole). Could the checks become ABI-version aware, so that rebuilds and redistribution are kept to a minimum? Maybe Timo is already keeping API/ABI stability between minor updates, so the version checks should be against the first two version components only. Thanks! -- http://thimm.gr/ - http://ATrpms.net/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20101018/af8df024/attachment-0002.bin>
On Mon, 2010-10-18 at 09:22 +0300, Axel Thimm wrote:> Could the checks become ABI-version aware, so that rebuilds and > redistribution are kept to a minimum? Maybe Timo is already keeping > API/ABI stability between minor updates, so the version checks should be > against the first two version components only.I keep APIs source compatible whenever possible, but ABIs haven't been very stable in v2.0.x. So I would have had to bump the ABI version for every release anyway. :) But yeah, it would be nice at some point if this version check checked for actual ABI versions. The bad thing about that is that then I'd have to remember to update it whenever I actually change something..