-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
papd - CUPS 3.0 Support Roadmap. #663
Comments
Update: I now have papd working with libcups3 and printing documents. Discovered a bug in libcups3 in the process (see linked issue above). Now that issue has been fixed, I can proceed. |
@NJRoadfan One more task for this ticket is to update the documentation. At least the papd.conf(5) man page talks about using PPD files with CUPS. |
One can still override CUPS created queues with a custom PPD. That functionality has been retained. The only "under the hood" difference is that papd now dynamically generates a PPD on the fly by querying a printer via IPP directly, instead of relying on CUPS to do it (since its going away in 3.0). |
Right, so I think this behavior should be captured in the docs, for instance. |
For the record, I tweaked the papd docs slightly while merging #1374 to explain the new PPD behavior. |
print_cups.c
.print_cups.c
to allow papd to compile against bothlibcups2
andlibcups3
.cupsfilters
installed too.pkg-config
to detectlibcups3
andlibcupsfilters
.cups-config
script to detect the presence of CUPS. This script is going away with CUPS 3.x and the project is opting to usepkg-config
for now on. A preferred flow would be to keep the currentcups-config
macro routine in place to detect pre-3.x releases of CUPS, and if it fails, run the newerpkg-config
macro to check for CUPS 3.x andlibcupsfilter
.Currently the completion time frame of this list is TBD as CUPS 3.0 is not out yet. However, the API changes have been documented to allow for code updates. Project maintainers are targeting release later this year and distributions using CUPS 3.0 (notably Ubuntu) will likely appear shortly thereafter.
The text was updated successfully, but these errors were encountered: