On 2018-03-09 15:18 -0300, Herbert Fortes wrote:
> Hi Sven Joachim,
>
>>> My conclusion is that it is very risky to allow such combinations, and
>>> to rule them out I propose to change the package name of the cdk
>>> library, say to libcdk5a. It would then have to build-depend on
>>> libncurses-dev (>= 6.1+20180210) to ensure that it is linked against
>>> libncurses6 and not libncurses5. Of course this can only be uploaded
>>> to experimental for now, but should go to unstable when the ncurses
>>> transition starts there.
>
>
> I am OK with changing the name. But libcdk5a does not say
> much about why the change.
>
> Since the package name will change because of SONAME of
> libncurses, I thought to follow the SONAME of the library.
Well, the SONAME of the cdk library does not change with my proposal.
> libcdk5-6
If you like that better than libcdk5a, choose it. Or any other name,
it's rather arbitrary anyway.
> But maybe this will cause misunderstanding. The change is
> on version 6.1+20180210.
That's why the build-dependency on libncurses-dev (>= 6.1+20180210) is
needed.
I am not sure we understand each other yet, but I'm happy to answer
questions.
Cheers,
Sven
