Go to file
rtlhq faa12853c7 Import Debian changes 1.1.0 2023-01-31 20:16:05 +08:00
debian Import Debian changes 1.1.0 2023-01-31 20:16:05 +08:00
po Import Upstream version 1.1.0 2023-01-31 20:11:52 +08:00
src Import Upstream version 1.1.0 2023-01-31 20:11:52 +08:00
tools Import Upstream version 1.1.0 2023-01-31 20:11:52 +08:00
.editorconfig Import Upstream version 1.1.0 2023-01-31 20:11:52 +08:00
CMakeLists.txt Import Upstream version 1.1.0 2023-01-31 20:11:52 +08:00
COPYING Import Upstream version 1.1.0 2023-01-31 20:11:52 +08:00
COPYING.LIB Import Upstream version 1.1.0 2023-01-31 20:11:52 +08:00
Changelog Import Upstream version 1.1.0 2023-01-31 20:11:52 +08:00
DebconfKDEConfig.cmake.in Import Upstream version 1.1.0 2023-01-31 20:11:52 +08:00
Doxyfile Import Upstream version 1.1.0 2023-01-31 20:11:52 +08:00
Messages.sh Import Upstream version 1.1.0 2023-01-31 20:11:52 +08:00
README Import Upstream version 1.1.0 2023-01-31 20:11:52 +08:00
TODO Import Upstream version 1.1.0 2023-01-31 20:11:52 +08:00

README

Debconf-KDE
-----------

-------------------
General information
-------------------

This is libdebconf-kde, a library which provides a debconf frontend to present
questions asked during package installation on Debian-based systems.

A debconf frontend is something similar to a mail server; it gets commands from
a client and replies with a status code followed by a human readable message,
for instance "0 ok". When a program is installed in Debian, the 'config script'
(see man debconf-devel), acts as a client of a debconf frontend. Thus, different
frontends with different kind of user interfaces (kde/qt, gtk, text) can be used
to configure debian packages. This particular frontend is currently used by muon
and apper to configure packages.

While the clients for this protocol are oftenly the config scripts mentioned
above, other programs can use this protocol, for instance apt-listchanges has a
debconf interface, which allows muon to display the apt-listchanges messages
inside the muon user interface

-----------------------------------
Protocol used: the debconf protocol
-----------------------------------

The debconf protocol used by this software is explained here:
* /usr/share/doc/debian-policy/debconf_specification.html
* man 7 debconf-devel

There a are a couple of extensions of the protocol implemented in libdebconf-kde,
specifically these commands:
* X_PING - see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631769
* X_LOADTEMPLATEFILE - this is used by apt-listchanges, so providing it means
  apt-listchanges messages can be displayed by libdebconf-kde, see:
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678311