Ok.
> > Hi > I would talk with pkg-java folks on this matter > > https://packages.debian.org/sid/all/libcdk-java/filelist > their package has a libcdk-java library, so they might want to change their > source package to libcdk and let you use cdk again. > > Honestly libcdk-common sound weird when we have a libcdk-java there. > > So please try to solve with them first, because this kind of namespace > collisions are usually bad for the end users experience > > (If you read under the lines you can get my personal opinion, but it has been > some time since my last contribution on that team, so I won't share it as > java team member) > > cheers, > > G. > > ------------------------------ > Il mar 3 nov 2015 18:32 CET, Herbert Parentes Fortes Neto ha scritto: > > >Hi, > > > >> >Yes, in this case will be confusing. But let me > >> >share a point of view. > >> > > >> >The upstream tarball is cdk too. The package > >> >was libcdk at the beginning and then libcdk5. The 5 > >> >is about the ABI I believe. When the ABI change, it > >> >will be changed too. > >> > > >> >Suggestions ? > >> My suggestion is to call it libcdk (the source name) > >> and build a libcdk5 library > >> > >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=352961 > >> > >> it was removed the libcdk but just because of a SONAME bump. > >> > >> In my opinion the src name shouldn't change, just the library > >> should. > >> > >> BTW even libcdk5 might be fine, as long as they don't change soname too > >> often. > >> > >> but unfortunately cdk is misleading to me. > >> > >> what do you think about this? > >> > >> (please note: I don't have a strong opinion about this, but since we can't > >> have > >> cdk as source name, we should change it anyway) > > > >I started think about this because of this bug[0]. To > >close it I would build the libcdk5(-dev) and libcdkw5(-dev) > >packages and more a package with common files. Even that > >way libcdk5 and libcdkw5 must conflict because /usr/include/cdk > >have common files (just one is different, cdk_config.h if > >I remember correct). > > > >[0] - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=382294 > > > >As the upstream tarball is cdk I thought cdk-common. As > >is not possible, the package with common files would be > >libcdk-common ? > > > > > >regards, > >-- > >Herbert Parentes Fortes Neto (hpfn) > > > -- Herbert Parentes Fortes Neto (hpfn)
