Support sending client-info with cups* APIs
Add client-info and its member sub-attributes to the ipp_options array so that the attribute types are parsed correctly by cupsEncodeOption.
This is useful for sending client-info using cupsCreateDestJob or cupsStartDestDocument functions.
Not for 2.4.x. Needs privacy audit and explicit consent to send...
Understood, thanks. I'm a little bit confused about the consent part. Isn't the burden of getting the consent on the application using libcups?
@sparik libcups has to enforce the consent part, otherwise we are just relying on every application to do it...
Got it, thanks for the clarification.
Closing this PR - if you do end up syncing things with the current CUPS master code, we can re-open and continue looking at it...