Closed
Bug 1792248
Opened 3 years ago
Closed 3 years ago
Add a moz.yaml for cups and add it to Updatebot
Categories
(Core :: Printing: Setup, enhancement)
Core
Printing: Setup
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: tjr, Assigned: tjr)
References
Details
Attachments
(2 files)
The more things we can get cataloged by moz.yaml the better - it will give us a standardized format for a Software Bill of Materials.
Additionally, cups doesn't seem to change much, if ever, so tracking it with Updatebot will be very low-volume.
(Full disclosure: I picked cups because I needed a test subject for my 'only vendor a project subset' work.)
Assignee | ||
Comment 1•3 years ago
|
||
Depends on D158051
Updated•3 years ago
|
Assignee: nobody → tom
Status: NEW → ASSIGNED
Assignee | ||
Comment 2•3 years ago
|
||
Depends on D158052
Assignee | ||
Comment 3•3 years ago
|
||
From Emily McDonough on phab:
I don't think there is really much reason to update these headers as they are right now, for a few reasons:
Apple is no longer updating their CUPS repo on github
We dynamically open CUPS through the nsCUPSShim so unless we specifically need to use a new function or enum value there is no actual reason to update them (and when we do we should ensure that in the CUPS shim the new functions are marked as optional, and we have a fallback for when they are missing, as many distros have a woefully outdated CUPS version). On some systems we will be using older CUPS than the headers, on some newer.
If that is the case and we do want new headers for new functions or enum values, we should switch to using https://github.com/openprinting/cups as the upstream instead, as that is where actual development is happening moving forward.
So I'm going to wontfix this.
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•