Source: cpdb-libs
Section: net
Priority: optional
Maintainer: linuxmangaka <linuxmangaka@gmail.com>
Rules-Requires-Root: no
Build-Depends: debhelper-compat (= 13),
 autoconf,
 autotools-dev,
 dbus-daemon,
 libcups2-dev,
 libdbus-1-dev,
 libgdk-pixbuf-2.0-dev,
 libglib2.0-dev,
 libjpeg62-turbo-dev | libjpeg-turbo8-dev,
 libjpeg-dev,
 libtiff-dev,
 pkgconf,
 pkg-config,
 sharutils,
Standards-Version: 4.6.2
Homepage: https://github.com/OpenPrinting/cpdb-libs
Vcs-Browser: https://salsa.debian.org/printing-team/cpdb-libs
Vcs-Git: https://salsa.debian.org/printing-team/cpdb-libs.git

Package: libcpdb2
Section: libs
Architecture: any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends},
Depends: ${shlibs:Depends},
 ${misc:Depends},
Description: Frontend/Backend Communication Libraries for the Common Print Dialog Backends
 The Common Print Dialog Backends (CPDB) project of OpenPrinting is about separating the print dialogs of different GUI toolkits and applications (GTK, Qt, LibreOffice, Firefox, Chromium, ...) from the different print technologies (CUPS/IPP, cloud printing services, ...) so that they can get developed independently and so always from all applications one can print with all print technologies and changes in the print technologies get supported quickly. If one opens the print dialog, the dialog will not talk directly to CUPS, a cloud printing service, or any other printing system. For this communication there are the backends. The dialog will find all available backends and sends commands to them, for listing all available printers, giving property/option lists for the selected printer, and printing on the selected printer. This communication is done via D-Bus. So the backends are easily exchangeable and for getting support for a new print technology only its backend needs to get added.

#Package: libcpdb2t64
#Section: libs
#Architecture: any
#Multi-Arch: same
#Pre-Depends: ${misc:Pre-Depends},
#Depends: ${shlibs:Depends},
# ${misc:Depends},
#Provides: ${t64:Provides}
#Breaks: libcpdb2 (<< ${source:Version}),
#Replaces: libcpdb2,
#Description: Frontend/Backend Communication Libraries for the Common Print Dialog Backends
# The Common Print Dialog Backends (CPDB) project of OpenPrinting is about separating the print dialogs of different GUI toolkits and applications (GTK, Qt, LibreOffice, Firefox, Chromium, ...) from the different print technologies (CUPS/IPP, cloud printing services, ...) so that they can get developed independently and so always from all applications one can print with all print technologies and changes in the print technologies get supported quickly. If one opens the print dialog, the dialog will not talk directly to CUPS, a cloud printing service, or any other printing system. For this communication there are the backends. The dialog will find all available backends and sends commands to them, for listing all available printers, giving property/option lists for the selected printer, and printing on the selected printer. This communication is done via D-Bus. So the backends are easily exchangeable and for getting support for a new print technology only its backend needs to get added.

Package: libcpdb-frontend2
Section: libs
Architecture: any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends},
Depends: ${shlibs:Depends},
 ${misc:Depends},
 libcpdb2 (= ${binary:Version}),
Description: Frontend/Backend Communication Libraries for the Common Print Dialog Backends
 The Common Print Dialog Backends (CPDB) project of OpenPrinting is about separating the print dialogs of different GUI toolkits and applications (GTK, Qt, LibreOffice, Firefox, Chromium, ...) from the different print technologies (CUPS/IPP, cloud printing services, ...) so that they can get developed independently and so always from all applications one can print with all print technologies and changes in the print technologies get supported quickly. If one opens the print dialog, the dialog will not talk directly to CUPS, a cloud printing service, or any other printing system. For this communication there are the backends. The dialog will find all available backends and sends commands to them, for listing all available printers, giving property/option lists for the selected printer, and printing on the selected printer. This communication is done via D-Bus. So the backends are easily exchangeable and for getting support for a new print technology only its backend needs to get added.

#Package: libcpdb-frontend2t64
#Section: libs
#Architecture: any
#Multi-Arch: same
#Pre-Depends: ${misc:Pre-Depends},
#Depends: ${shlibs:Depends},
# ${misc:Depends},
# libcpdb2t64 (= ${binary:Version}),
#Provides: ${t64:Provides}
#Breaks: libcpdb-frontend2 (<< ${source:Version}),
#Replaces: libcpdb-frontend2,
#Description: Frontend/Backend Communication Libraries for the Common Print Dialog Backends
# The Common Print Dialog Backends (CPDB) project of OpenPrinting is about separating the print dialogs of different GUI toolkits and applications (GTK, Qt, LibreOffice, Firefox, Chromium, ...) from the different print technologies (CUPS/IPP, cloud printing services, ...) so that they can get developed independently and so always from all applications one can print with all print technologies and changes in the print technologies get supported quickly. If one opens the print dialog, the dialog will not talk directly to CUPS, a cloud printing service, or any other printing system. For this communication there are the backends. The dialog will find all available backends and sends commands to them, for listing all available printers, giving property/option lists for the selected printer, and printing on the selected printer. This communication is done via D-Bus. So the backends are easily exchangeable and for getting support for a new print technology only its backend needs to get added.

Package: libcpdb-backend-dev
Section: libdevel
Architecture: any
Multi-Arch: same
Depends: ${shlibs:Depends},
 ${misc:Depends},
 libcpdb2 (= ${binary:Version}) | libcpdb2t64 (= ${binary:Version}),
 libcpdb-dev (= ${binary:Version}),
Description: Frontend/Backend Communication Libraries for the Common Print Dialog Backends
 The Common Print Dialog Backends (CPDB) project of OpenPrinting is about separating the print dialogs of different GUI toolkits and applications (GTK, Qt, LibreOffice, Firefox, Chromium, ...) from the different print technologies (CUPS/IPP, cloud printing services, ...) so that they can get developed independently and so always from all applications one can print with all print technologies and changes in the print technologies get supported quickly. If one opens the print dialog, the dialog will not talk directly to CUPS, a cloud printing service, or any other printing system. For this communication there are the backends. The dialog will find all available backends and sends commands to them, for listing all available printers, giving property/option lists for the selected printer, and printing on the selected printer. This communication is done via D-Bus. So the backends are easily exchangeable and for getting support for a new print technology only its backend needs to get added.

Package: libcpdb-frontend-dev
Section: libdevel
Architecture: any
Multi-Arch: same
Depends: ${shlibs:Depends},
 ${misc:Depends},
 libcpdb-frontend2 (= ${binary:Version}) | libcpdb-frontend2t64 (= ${binary:Version}),
 libcpdb2 (= ${binary:Version}) | libcpdb2t64 (= ${binary:Version}),
 libcpdb-dev (= ${binary:Version}),
Description: Frontend/Backend Communication Libraries for the Common Print Dialog Backends
 The Common Print Dialog Backends (CPDB) project of OpenPrinting is about separating the print dialogs of different GUI toolkits and applications (GTK, Qt, LibreOffice, Firefox, Chromium, ...) from the different print technologies (CUPS/IPP, cloud printing services, ...) so that they can get developed independently and so always from all applications one can print with all print technologies and changes in the print technologies get supported quickly. If one opens the print dialog, the dialog will not talk directly to CUPS, a cloud printing service, or any other printing system. For this communication there are the backends. The dialog will find all available backends and sends commands to them, for listing all available printers, giving property/option lists for the selected printer, and printing on the selected printer. This communication is done via D-Bus. So the backends are easily exchangeable and for getting support for a new print technology only its backend needs to get added.

Package: libcpdb-dev
Section: libdevel
Architecture: any
Multi-Arch: same
Depends: ${shlibs:Depends},
 ${misc:Depends},
 libcpdb2 (= ${binary:Version}) | libcpdb2t64 (= ${binary:Version}),
Description: Frontend/Backend Communication Libraries for the Common Print Dialog Backends
 The Common Print Dialog Backends (CPDB) project of OpenPrinting is about separating the print dialogs of different GUI toolkits and applications (GTK, Qt, LibreOffice, Firefox, Chromium, ...) from the different print technologies (CUPS/IPP, cloud printing services, ...) so that they can get developed independently and so always from all applications one can print with all print technologies and changes in the print technologies get supported quickly. If one opens the print dialog, the dialog will not talk directly to CUPS, a cloud printing service, or any other printing system. For this communication there are the backends. The dialog will find all available backends and sends commands to them, for listing all available printers, giving property/option lists for the selected printer, and printing on the selected printer. This communication is done via D-Bus. So the backends are easily exchangeable and for getting support for a new print technology only its backend needs to get added.

Package: cpdb-libs-tools
Architecture: any
Depends: ${shlibs:Depends},
 ${misc:Depends},
 libcpdb2 (= ${binary:Version}) | libcpdb2t64 (= ${binary:Version}),
Breaks: libcpdb-libs-common-dev (<< 1.2.0-1~),
 libcpdb-libs-tools (<< 2~),
Replaces: libcpdb-libs-common-dev (<< 1.2.0-1~),
 libcpdb-libs-tools (<< 2~),
Description: Frontend/Backend Communication Libraries for the Common Print Dialog Backends
 The Common Print Dialog Backends (CPDB) project of OpenPrinting is about separating the print dialogs of different GUI toolkits and applications (GTK, Qt, LibreOffice, Firefox, Chromium, ...) from the different print technologies (CUPS/IPP, cloud printing services, ...) so that they can get developed independently and so always from all applications one can print with all print technologies and changes in the print technologies get supported quickly. If one opens the print dialog, the dialog will not talk directly to CUPS, a cloud printing service, or any other printing system. For this communication there are the backends. The dialog will find all available backends and sends commands to them, for listing all available printers, giving property/option lists for the selected printer, and printing on the selected printer. This communication is done via D-Bus. So the backends are easily exchangeable and for getting support for a new print technology only its backend needs to get added.

Package: libcpdb-libs-tools
Section: oldlibs
Architecture: all
Depends: ${shlibs:Depends},
 ${misc:Depends},
 cpdb-libs-tools,
Description: Frontend/Backend Communication Libraries for the Common Print Dialog Backends
 The Common Print Dialog Backends (CPDB) project of OpenPrinting is about separating the print dialogs of different GUI toolkits and applications (GTK, Qt, LibreOffice, Firefox, Chromium, ...) from the different print technologies (CUPS/IPP, cloud printing services, ...) so that they can get developed independently and so always from all applications one can print with all print technologies and changes in the print technologies get supported quickly. If one opens the print dialog, the dialog will not talk directly to CUPS, a cloud printing service, or any other printing system. For this communication there are the backends. The dialog will find all available backends and sends commands to them, for listing all available printers, giving property/option lists for the selected printer, and printing on the selected printer. This communication is done via D-Bus. So the backends are easily exchangeable and for getting support for a new print technology only its backend needs to get added.