On Fri, 2007-04-27 at 13:56 -0400, Ari Pollak wrote: > This isn't necessarily something you would have to do. A > versioned /usr/lib/libpurple that changed with the major version of > libpurple when the API/ABI breaks would be similar to what most other > libraries do, and would make it easier for dependent programs and me.
Umm, we version the entire Pidgin project as if it was a library. If we're lacking soversion magic, we can fix that, but once we get 2.0.0 out the door, it can be packaged as libpurple2 safely. API/ABI won't be broken until 3.0.0, by definition. We do *add* APIs, but that results in an increase in the minor version. Richard
signature.asc
Description: This is a digitally signed message part
