DragonFly submit List (threaded) for 2008-07
Re: libevent upgrade from 1.3e to 1.4.5-stable
"Antonio Huete Jimenez" <email@example.com> wrote in message
Here's a working patch for upgrading libevent. It compiles just fine and
I'm currently using in one of my DFBSD machines.
Bug fixes can be found in:
I don't have the oportunity of checking with bluetooth because I don't
have any device, so if someone has devices and time, please check.
About ABI changes, there are some functions that have been removed, and
some parameters slightly changed:
Considering the primary rationale for importing libevent (to my knowledge)
Samuel Greear (sjg), I invite you to give your opinion here just like at
* Please, consider your environment before printing this email
tuxillo at EFNet in #dragonflybsd
support libbluetooth, and given that it is readily available via pkgsrc and
known to have an unstable ABI. Wouldn't it make the most sense (short of
rewriting libbluetooth not to use libevent) to either move libevent into a
subdirectory of libbluetooth and link it directly into libbluetooth,
dropping the manpages. Or, expose it as dflibevent or similar noting
that it is generally intended for base system use and third party binary
applications should not expect it to maintain a stable ABI? My preference
be toward the former more than the latter, at least until some other
libevent hits base. Either way it would pretty much eliminate any ABI
concerns which fly in the face of a preference to upgrade the library upon
new release. I would think the ideal would be for third party applications
prefer pkgsrc for something like this. ABI breakage is probably no big deal
current but could get bumpy down the road (I'm not sure how this would
into process checkpointing in the case of restoring a libevent-dependant
elsewhere, where libevent exposes a different binary interface). In any
maintenance and updates of select and poll support for libevent can likely
pulled from the tree.
I can prepare a patch if there is some kind of consensus.