Bug#430422: Changing omniorb4 source package name

2007-10-24 Thread Philipp Kern
Hi Thomas, On Thu, Oct 18, 2007 at 04:57:32PM +0200, Thomas Girard wrote: > > [0] I don't know how much the API changed. I guess that the standarised > > CORBA API is still supposed to work as before? > The C++ mapping conformance was updated to a more recent version, so > possibly any applica

Bug#430422: Changing omniorb4 source package name

2007-10-18 Thread Thomas Girard
Le jeudi 18 octobre 2007 à 16:57 +0200, Thomas Girard a écrit : > According to the Debian Policy[1], we can choose "to support only one > development version a time". In our case, the libraryname is libomniorb4 > and the SONAME version[2] is changing from 0 to 1. I forgot to add that given this d

Bug#430422: Changing omniorb4 source package name

2007-10-18 Thread Thomas Girard
Le jeudi 18 octobre 2007 à 15:21 +0200, Philipp Kern a écrit : > On Thu, Oct 18, 2007 at 02:57:34PM +0200, Thomas Girard wrote: > > Having thought about this again for a while, I'm no longer convinced we > > should change the source package name. Indeed, the API was changed, but > > we are not goin

Bug#430422: Changing omniorb4 source package name (was: Re: Bug#430422: omniorb4: Out of date / python2.5 transition)

2007-10-18 Thread Philipp Kern
On Thu, Oct 18, 2007 at 02:57:34PM +0200, Thomas Girard wrote: > Having thought about this again for a while, I'm no longer convinced we > should change the source package name. Indeed, the API was changed, but > we are not going to support both omniorb4.0 and omniorb4.1. > > omnievents, which bui

Bug#430422: Changing omniorb4 source package name (was: Re: Bug#430422: omniorb4: Out of date / python2.5 transition)

2007-10-18 Thread Thomas Girard
Hi all, > is the question if it's (intended to be) fully API compatible, then the > source package could just me updated. > > > The library packages do change name (from foo4 to foo4-1) due to the > > soname change, so anyone depending on it (i.e. omnievents) will be > > broken until they are reb