On 09/27/2015 10:13 AM, Didier 'OdyX' Raboud wrote:
Indeed, it seems that you can't. I can confirm that cups and foomatic-filters are not coinstallable, at least since jessie.
The most important part of foomatic-filters, foomatic-rip, is included in cups-filters, only thing not included is beh.
Till: should 'beh' be shipped in cups-filters too, or is there an alternative to it between cups and cups-filters. Alternatively, should we split 'beh' off foomatic-filters?
Reasons why I did not overtake beh into cups-filters:1. beh is written in Perl and nothing in cups-filters is written in Perl, so the rarely used beh would introduce a new dependency. It seems that the only interpreter language in the core part of Linux distributions is Python. Volunteers for "translating" beh to C are welcome.
2. beh with standard permissions only works with backends with standard permissions. root-only backends (with executable bit only for root) only work through beh if one assigns the same root-only permissions to beh, making also normal backends used through beh running as root. Any suggestions for handling this permission problem are welcome.
3. beh is very rarely asked for as CUPS by itself offers at least some configurability for backend failure handling for years now.
As a quick solution on the side of the distribution I would split the binary packages of foomatic-filters to have one containing foomatic-rip (for the rare non-CUPS printing system users) and one containing beh (for the rare cups+beh users).
An upstream solution would require solving (1) and (2) above with (3) demotivating me from this somewhat. Volunteers welcome.
Till