On Sat, Apr 17, 2010 at 11:40:36AM +0200, Lars Marowsky-Bree wrote: > Lars, I have no other way of saying this, but I still think you're > completely misguided in this desire to preserve binary compatibility.
> What's the point in preserving local ABI compatibility if they have to > restart everything anyway? Situation is: I had pacemaker 1.0.8 installed. There is no pacemaker 1.0.9 yet. Cluster glue is updated. I install updated cluster glue, as it better supports pacemaker 1.0.8. I do that, and boom, all my stack segfaults. Why would I require my users to fetch new builds of the very same version of heartbeat and pacemaker, if it is easily avoided? Why would I knowingly break ABI compatibility, if I can avoid it, just for two ints added at the end of a struct instead of in the middle? > I have absolutely no understanding for your desire to keep this ABI > compatible and make code more complicated by needing to support You don't need to support different semantics. If you want to only support the new semantics, require the 2.1 library. Done. Whether you require 3.0 or 2.1 does not make a difference to you, does it. > Anyway, I've had my say. -- : Lars Ellenberg : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com DRBD® and LINBIT® are registered trademarks of LINBIT, Austria. _______________________________________________________ Linux-HA-Dev: [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
