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. libcdk5-6 But maybe this will cause misunderstanding. The change is on version 6.1+20180210. Regards, Herbert
