Comment 8 for bug 820820

There are two sides to this story. Those who only use pure PDF documents and who need something to print them to a spool, and those who actually want to be able to manipulate the output via Ghostscrpt first. The main issue with the PDF workflow patch was that it prevented those who want to manipulate the output via cups-pdf.conf Ghostscript options from doing so; it hard-coded too many things and it removed upstream functionality from CUPS-PDF. That produced endless criticism against the patch's impact upon the package's lost flexibility. If someone ever came up with a less intrusive version of this patch, upstream would gladly merge it.