569a60c2de
event framework to STOP_AT_FIRST, and then moves a bunch of side-effect-inducing code in the libevent2019 configure.m4 up to POST_CONFIG. == More detail == Change the event framework from STOP_AT_FIRST_PRIORITY to STOP_AT_FIRST. This means that only one component can win (vs. all STOP_AT_FIRST_PRIORITY, in which multiple components of the same priority can all win). You still need to ensure that there are no side-effects from the winner, however, so check for winning during POST_CONFIG, and set things like the base_include there. This simplifies the configury quite a bit -- you don't have to assume that mulitple components can win: zero or one components will win. Also change the libevent 2019 priority to 50 so that some other (developer-specific/local) component could win, if it wanted to. This commit was SVN r27794.