Comment 37 for bug 2003259

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Checked through everything whether I have nothing forgotten, seems that I overlooked the question with the ppdc.

The ppdc is actually only needed for development and debugging:

- CUPS 2.x needs ppdc as external executable, but it has its own ppdc.

- Printer Applications (the PPD/driver-retro-fitting ones) manage collections of PPDs (including *.drv files) with libppd's API for PPD collections and these call the library functions for the ppdc functionality directly (the functions are in libppd), without needing an external executable.

- CUPS 3.x does not support PPD files (and also not *.drv files) at all, so it will not need ppdc.

The code in the ppdc binary package is actually only wrappers which call corresponding library functions. The actual functionality is completely in libppd.

So an actual promotion of ppdc is not needed, but ppdc should not add any extra risks due to its functionality already residing in libppd.