Well, my point was that as of now, /usr/lib/libpurple is, for the most part, unversioned, and libpurple has a version of 0.0.0. The latter is not really a problem as long as it will get incremented appropriately, and I'd just have to call the package libpurple0.
On Fri, 2007-04-27 at 13:23 -0500, Richard Laager wrote: > 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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
