Re: upgrade orfeotoolbox to 5.0

[Rashad M <mohammedrashadkm@gmail.com>]

Hi Bas,

On Mon, Sep 28, 2015 at 10:18 AM, Bas Couwenberg <sebastic@xs4all.nl> wrote:

On 2015-09-28 10:13, Bas Couwenberg wrote:

On 2015-09-28 09:51, Rashad M wrote:

I had added .symbols file for libotb package.

http://anonscm.debian.org/cgit/pkg-grass/otb.git/commit/?id=9d06c6e9fcf334e283decc8918559d5d368d85d0

If this seems okay I will add do the same for libotb-commandline,
libotb-apps etc..

Can you have a look?

Since you're not using pkgkde-symbolshelper optional/template symbols
aren't marked as such, this will cause FTBFS on other architectures.
If you want to use symbols files for C++ projects you need to use
pkgkde-symbolshelper and override dh_makeshlibs to use -c0 to not fail
the build when symbols change. This method requires uploads to
experimental first to gather the symbols for the other architectures.
See for example this commit that implemented symbols handling with
pkgkde-symbolshelper for the mapserver package:

Apparently hit a Send hotkey, the commit in question is:

http://anonscm.debian.org/cgit/pkg-grass/mapserver.git/commit/?id=e959923d5c1cb8de4312b5d24315a6b96a1f2718

If you don't want to do the experimental uploads, you should use shlibs files instead. This allows you to require a higher version of the otb packages even if the SONAME and related package name doesn't change.

I will update the symbols file with pkgkde-symbolshelper. I will get back to this probably by end of this week.

Q: currently I haven't done moving shared library into separate package. I hope to do that after getting the packages into experimental. Is that okay?. Splitting files into separate .install is easy but I need to build the dependencies in the control file. This seems not trivial... unless I am missing something.

Q: What all should be done other than symbols file

Kind Regards,

Bas

--

Regards,
   Rashad