CAPS Universe documentation  1.0.4
All you need to know to be successful
Install Printing Coordinator

The corresponding:

An Installing Example

All build instructions in the sections above will use default paths which might not be suitable for your system. So the filesystem paths CAPS will use in the filesystem must be defined manually. You should use the same settings like you have used for libcapsbase.

Like the example in the libcapsbase a simple but useful configuration can be:

./configure --prefix=/usr

Other configuration parameters are the same for caps-printing-coordinator than for libcapsbase:

Special Configuration Parameters

Some configuration parameters are special to this package. The caps-printing-coordinator needs to parametrize DBUS and systemd and thus, needs to store some config files and unit files. In order to do so, it might need help where to store these files:

DBUS Service Unit

The printing coordinator starts on demand if someone attaches to its DBUS bus interface. This needs some setup in conjunction with systemd and a DBUS service file needs to be stored where the DBUS executable expects it:

--with-dbussystemservicedir=<some DIR>
Note
This directory is auto detected. You need to overwrite it only for special use cases.

DBUS Service Policy

The printing coordinator attaches to the DBUS system-wide bus, and thus, all clients and printer drivers need to do so as well. The CAPS DBUS policy configuration permits this and needs to be stored where the DBUS executable expects it:

--with-dbussystempolicydir=<some DIR>
Note
This directory is auto detected. You need to overwrite it only for special use cases.

systemd Unit File

The executable gets launched by systemd and thus, requires a corresponding unit file. This file needs to be stored where systemd expects it:

--with-systemdsystemunitdir=<some DIR>
Note
This directory is auto detected. You need to overwrite it only for special use cases.