Comment 19 for bug 1747759

I have updated CPDB (cpdb-libs, cpdb-backend-cups, cpdb-backend-file) to the current 2.x versions from upstream, as needed by current GTK (4.9.4). There the binary packages are renamed. Therefore I am updating this part:

List of specific binary packages to be promoted to main:

- libcpdb2
- libcpdb-frontend2

- libcpdb-dev
- libcpdb-frontend-dev
- libcpdb-backend-dev

Specific binary packages built, but NOT to be promoted to main:

- cpdb-libs-tools

cpdb-libs provides 2 library packages, both should to go to main. They implement the CPDB protocol. Frontends (print dialogs) need both, backends need only the first one. As they are libraries they usually do not need to get seeded, they will get pulled in through dependencies of the packages containing print dialogs or CPDB backends, especially now cpdb-backend-cups and cpdb-backend-file (see the other MIRs) and also GTK (4.9.4+) and later Qt (version TBD).

libcpdb2
libcpdb-frontend2

These are the headers and other development files, to be treated as usually -dev files of libraries in Main are treated. The third package is for convenience, so that if you want to create/build a backend, you build-depend only on libcpdb-backend-dev and if you want to to create/build a frontend you simply build-depend on libcpdb-frontend-dev.

libcpdb-dev
libcpdb-frontend-dev
libcpdb-backend-dev

This is actually only an example/demo frontend, it is actually used by the autopkgtests for this package (cpdb-libs) and for cpdb-backend-file. Can stay in Universe. Or should this be merged into the libcpdb-frontend-dev binary package then?

cpdb-libs-tools