Differences between revisions 2 and 3
Revision 2 as of 2007-06-26 09:13:41
Size: 1314
Editor: ?goneri
Comment:
Revision 3 as of 2007-06-26 09:53:52
Size: 1471
Editor: ?goneri
Comment:
Deletions are marked like this. Additions are marked like this.
Line 35: Line 35:
There is an ABI breakage between de 0.5 and the 0.8 release of libode. There is an ABI breakage between de 0.5 and the 0.8 release of libode but both share the same SONAME: libode.so.0
Line 37: Line 37:
Today, a libode0c2 0.8 package had been a uploaded in unstable and we think it's not a good idea since it breaks the depending package. To sort this out we want to upload a new libode0c2 0.5 package (with an EPOCH) and upload a libode0c2a 0.8 package. Today, a libode0c2 0.8 package had been a uploaded in unstable and we think it's not a good idea since it breaks the depending package. To sort this out we probably need to upload a new libode0c2 0.5 package (with an EPOCH).

For the transition itself we think we need to rename the package.
Line 50: Line 52:
http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html

Hello,

libODE is a free, industrial quality library for simulating articulated rigid body dynamics - for example ground vehicles, legged creatures, and moving objects in VR environments. It is fast, flexible, robust and platform independent, with advanced joints, contact with friction, and built-in collision detection.

$apt-cache --recurse rdepends libode0c2 libode0c2 Reverse Depends:

  • xmoto python-pyode libode0-dev xmoto python-soya python-pyode python-pyepl libode0-dev

python-pyepl Reverse Depends: python-soya Reverse Depends:

  • slune python-soya-doc balazar

balazar Reverse Depends: python-soya-doc Reverse Depends:

  • python-soya

slune Reverse Depends:

  • python-soya junior-games-gl

junior-games-gl Reverse Depends:

There is an ABI breakage between de 0.5 and the 0.8 release of libode but both share the same SONAME: libode.so.0

Today, a libode0c2 0.8 package had been a uploaded in unstable and we think it's not a good idea since it breaks the depending package. To sort this out we probably need to upload a new libode0c2 0.5 package (with an EPOCH).

For the transition itself we think we need to rename the package.

Then we will ask maintainers of this package to depend on libode0c2:

  • python-pyode libode0-dev xmoto python-soya python-pyode python-pyepl

http://packages.debian.org/libode0c2 http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html