On Fri, Jul 13, 2018 at 3:08 PM, Anatol Belski <a...@php.net> wrote: >> I ask, because my release builder for 7.2 (and 7.1 if Joe is using >> Davey's builder) is using re2c 0.13.5 . I don't imagine the risk of >> updating re2c mid-relase is particularly high, but it is non-zero. >> > Normally RMs would define the tool versions that are expected > to be stable and that are always used for the official tarballs. > In the case of 7.0, it'd be always re2c 0.13.5 and bison 3.0.2, > where ever I'd produce the tarball (even I don't always use > Jessie for packaging). We probably should take this into the > release process docs, if it isn't there already. > Well, whichever version we've settled on, I've updated sgolemon/php-release to allow using arbitrary versions of re2c. https://github.com/sgolemon/php-release/commit/9197257bc6f2f607476f950733a0c13ab5e3e867
If RE2C_VERSION is set to 1.0.3, it'll swap in the pre-built 1.0.3 binary I've included in the package. Otherwise, it'll clone the source repo, checkout the requested tag (or commit hash) and build that). I'll plan on doing 7.2.9+ with 1.0.3 (unless we decide differently by then). Remi should stick to 0.13.5 (default) for 7.2.8-final as previously stated. Doing a dry-run now to see how it looks. -Sara -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
