Discussion:
[omniORB] OmniORB 4.1.0 API backwards compatibility
Floris Bruynooghe
2007-10-04 19:56:16 UTC
Permalink
Hello

While working on the Debian packages for omniORB 4.1.0 [1] we where
wondering if the API of it is completely backwards compatible to
omniORB 4.0.[67]. The soname would suggest so I think, as that would
have been bumped to 5.0.0 otherwise, or am I wrong here?

I.e., if something was compiled against omniORB 4.0.7, will it compile
against 4.1.0?

Cheers
Floris

[1] http://alioth.debian.org/projects/pkg-corba
--
Debian GNU/Linux -- The Power of Freedom
www.debian.org | www.gnu.org | www.kernel.org
Matej Kenda
2007-10-04 20:42:01 UTC
Permalink
Hi Floris,

The API is not completely backwards compatible. Details about the
changes are listed in release notes
http://omniorb.cvs.sourceforge.net/omniorb/omni/ReleaseNotes.txt?revision=1.1.2.9&view=markup&pathrev=omni4_1_develop

I have already worked on debian packaging for 4.1.x. I have modified
Ubuntu Feisty Fawn packaging files for 4.0.6.

Please find attached the modified files.

Regards,

Matej
Post by Floris Bruynooghe
Hello
While working on the Debian packages for omniORB 4.1.0 [1] we where
wondering if the API of it is completely backwards compatible to
omniORB 4.0.[67]. The soname would suggest so I think, as that would
have been bumped to 5.0.0 otherwise, or am I wrong here?
I.e., if something was compiled against omniORB 4.0.7, will it compile
against 4.1.0?
--
Matej Kenda, Senior Software Engineer
HERMES SoftLab d.d. (www.hermes-softlab.com), Slovenia
-------------- next part --------------
A non-text attachment was scrubbed...
Name: debian.tar.gz
Type: application/x-gzip
Size: 5991 bytes
Desc: not available
Url : http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20071004/5d433952/debian.tar.bin
Floris Bruynooghe
2007-10-05 02:21:16 UTC
Permalink
Hello Matej
Post by Matej Kenda
The API is not completely backwards compatible. Details about the
changes are listed in release notes
http://omniorb.cvs.sourceforge.net/omniorb/omni/ReleaseNotes.txt?revision=1.1.2.9&view=markup&pathrev=omni4_1_develop
I did notice that, but could not make out if it was just a change from
the beta to the final releas, or also affected a 4.0.x -> 4.1.x
transition. I.e. if it was a change in a part of the API only added
in the 4.1 branch then it doesn't affect the stable release
transitions.
Post by Matej Kenda
I have already worked on debian packaging for 4.1.x. I have modified
Ubuntu Feisty Fawn packaging files for 4.0.6.
Please find attached the modified files.
Cool, did you check out the packages I made earlier (as announced on
this list on 30 May 2007) too? They did a lot of the things already
and a few more. In particular they close a few bugs in the Debian BTS
and rename a few binary packages as you can't do an ABI (new soname)
transition withouth changing package names. Also if the API indeed
changed then the entire package will need to be change to reflect
this, i.e. you can't call it omniorb4 anymore.

But as I said, currently we're working on updating the packages in
Debian at [1], so you can check out the svn archive at [2] as it
contains even more improvements. Feel free to check it out and
contribute if you find problems with it or find things you did better!
You can always contact us on the pkg-corba mailing list.


Regards
Floris

[1] http://alioth.debian.org/projects/pkg-corba/
[2] http://svn.debian.org/wsvn/pkg-corba
Post by Matej Kenda
Regards,
Matej
Post by Floris Bruynooghe
Hello
While working on the Debian packages for omniORB 4.1.0 [1] we where
wondering if the API of it is completely backwards compatible to
omniORB 4.0.[67]. The soname would suggest so I think, as that would
have been bumped to 5.0.0 otherwise, or am I wrong here?
I.e., if something was compiled against omniORB 4.0.7, will it compile
against 4.1.0?
--
Matej Kenda, Senior Software Engineer
HERMES SoftLab d.d. (www.hermes-softlab.com), Slovenia
--
Debian GNU/Linux -- The Power of Freedom
www.debian.org | www.gnu.org | www.kernel.org
Matej Kenda
2007-10-05 12:53:57 UTC
Permalink
Hi Floris
Post by Floris Bruynooghe
Post by Matej Kenda
I have already worked on debian packaging for 4.1.x. I have modified
Ubuntu Feisty Fawn packaging files for 4.0.6.
Please find attached the modified files.
Cool, did you check out the packages I made earlier (as announced on
this list on 30 May 2007) too? They did a lot of the things already
and a few more. In particular they close a few bugs in the Debian BTS
and rename a few binary packages as you can't do an ABI (new soname)
transition withouth changing package names. Also if the API indeed
changed then the entire package will need to be change to reflect
this, i.e. you can't call it omniorb4 anymore.
I took the debian directory from the source package of the Feisty deb
(http://packages.ubuntu.com/feisty/devel/omniorb4) and modified it.

Please find attached the diff of the changes that I made to make the
installation work for me.
Post by Floris Bruynooghe
But as I said, currently we're working on updating the packages in
Debian at [1], so you can check out the svn archive at [2] as it
contains even more improvements. Feel free to check it out and
contribute if you find problems with it or find things you did better!
You can always contact us on the pkg-corba mailing list.
I'll take a look at the files in the svn repository.

Regards,

Matej
--
Matej Kenda, Senior Software Engineer
HERMES SoftLab d.d. (www.hermes-softlab.com), Slovenia
-------------- next part --------------
A non-text attachment was scrubbed...
Name: debian-pkg.diff
Type: text/x-diff
Size: 6863 bytes
Desc: not available
Url : http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20071005/2e3d2f1e/debian-pkg.bin
Loading...