Sean Kellogg <[EMAIL PROTECTED]> writes: > Would it be better to just keep the binary package as libmtp so that > end users don't have to hunt around for the correct package should > upstream continue to be a moving target?
The problem is that between end user and libmtp, you have an application (like amarok for instance) which expects a specific soname. Your proposal would need amarok to depend on libmtp version B while other package may still require version B. In other words, you'd need to synchronise the release of new version of libmtp with new version of *all* application that use libmtp. This would be a nightmare. HTH -- Dominique Dumont "Delivering successful solutions requires giving people what they need, not what they want." Kurt Bittner -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
