Bug#809312: RFS: otb/5.2.0+dfsg-1 [ITP] -- Orfeo Toolbox

[Rashad Kanavath <rashad.kanavath@c-s.fr>]

Hi Ghislain,

debian policy for shared library says each library must be in a seperate 
package [1].

OTB is well modularaized since 5.0.0. This allows external apps or 
libaries to use have some of the otb libs not all

For instance,
monteverdi required only a small subset of libs:
  OTBApplicationEngine
  OTBQtWidget
  OTBImageIO
  OTBVectorDataIO
  OTBTestKernel
  OTBCarto
  OTBProjection
  OTBStatistics

So splitting a shared library is useful there. It also aslo true for 
remote modules. If anyone want to write a remote module that depends on 
two other modules OTBCommon, OTBTestKernel. he don't need to drag in all 
dependencies for that.

And in future otb may have more modules. If there is a problem with 
split up libraries, I can change it and make it simply libotb and libotb-dev

What do you think?

[1] https://www.debian.org/doc/debian-policy/ch-sharedlibs.html