On Wed, Apr 19, 2006 at 08:39:25AM +0200, marc wrote: > Jelmer Vernooij wrote: > >On Tue, 2006-04-18 at 15:19 +0200, Marc Cromme wrote: > >This is actually correct. The package in testing is called libnunit-cil > >- NOT libnunit2.2.6-cil. The nunit=2.2.7 source package generates a > >libnunit2.2.6-cil package because 2.2.7 and 2.2.6 are API compatible. > >See the CLI policy for details. How is this causing you problems? > However, I find it still very odd that the nunit source package version > 2.2.7-1 produces a binary package called libnunit2.2.6-cil, because it > is binary compatible with the 2.2.6 version in testing, which by the way > is called libnunit-cil and not libnunit2.2.6-cil ??
> Wouldn't it better that the numbering fits such that nunit 2.2.7-1 > generates a binary package named libnunit2.2.7-cil, > I think this numbering business is a major source of confusion ... See the CLI policy for the reasoning behind this. This works similarly to sonames for standard packages (e.g. the GTK+ 2.14.1 package is still called 'libgtk2.0-0'. Cheers, Jelmer -- Jelmer Vernooij <[EMAIL PROTECTED]> - http://jelmer.vernstok.nl/
signature.asc
Description: Digital signature
