On 2015/10/15 20:50, Todd C. Miller wrote: > On Thu, 15 Oct 2015 22:22:17 -0400, "Ted Unangst" wrote: > > > Secondary question: what's involved in updating lex? I didn't realize we had > > fallen behind as it were, but should we switch too? > > At one point it required GNU m4'isms we didn't support (the -P > flag). We've had that for some time so I could take my merge of > flex 2.5.35 and update it to the latest (2.5.39) if there is interest. > > - todd
When I tried updating this at p2k9 there was a little fallout in base and ports, some of that has probably gone away now but if we want to do this, it's worth doing a bulk build with it first (I can do that). FWIW, OSX and FreeBSD had stuck with 2.5.4 for quite a long time, but they have both moved to a more recent version now. If this does get updated in base, there are currently about 20 ports which could move back to it (currently they're using 2.5.39 that is in ports) - cad/openscad databases/virtuoso devel/acpica devel/dtc editors/libreoffice geo/qgis graphics/digikam-kde4 multimedia/gstreamer-0.10/core multimedia/gstreamer1/core multimedia/libaacs multimedia/libbluray net/amule net/icinga/core2 net/knot www/chromium www/iridium www/webkit www/webkitgtk4 x11/qt5 Partly related, if there are any m4 wizards idling (as if!), there are a few porters who would be very happy if /usr/bin/m4 could be taught how to deal with newer bison...
