Patrice, thank you very much for your test results. Now I understand this bug:
On a new installation it easily happens that CUPS is not yet installed and started when the post-install script of cups-bsd is executed. The script only works on creating the /etc/printcap link if /etc/cups/cupsd.conf exists, which requires CUPS to be installed. In addition it links to /var/run/cups/printcap only if the file exists, which requires the CUPS daemon already to be running, To assure that CUPS is already running before the script gets started, we would need to make cups-bsd depend on CUPS, but this is not required for any other functionality of cups-bsd. The main functionality is to provide command line printing utilities which are compatible to the ones of BSD's LPD. These can be used without the cups package to be installed on the local machine, by specifying a remote CUPS server in /etc/cups/client.conf.
Therefore I will move the /etc/printcap functionality to the cups package, to avoid introducing a new dependency. The impact to the system is small, only some bytes for a symlink.
Patrice, thank you very much for your test results. Now I understand this bug:
On a new installation it easily happens that CUPS is not yet installed and started when the post-install script of cups-bsd is executed. The script only works on creating the /etc/printcap link if /etc/cups/ cupsd.conf exists, which requires CUPS to be installed. In addition it links to /var/run/ cups/printcap only if the file exists, which requires the CUPS daemon already to be running, To assure that CUPS is already running before the script gets started, we would need to make cups-bsd depend on CUPS, but this is not required for any other functionality of cups-bsd. The main functionality is to provide command line printing utilities which are compatible to the ones of BSD's LPD. These can be used without the cups package to be installed on the local machine, by specifying a remote CUPS server in /etc/cups/ client. conf.
Therefore I will move the /etc/printcap functionality to the cups package, to avoid introducing a new dependency. The impact to the system is small, only some bytes for a symlink.