Closed Bug 568278 Opened 15 years ago Closed 15 years ago

Avoid the license police: fix Sparkle license again after recent update

Categories

(Camino Graveyard :: General, defect)

All
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: alqahira, Assigned: alqahira)

Details

Attachments

(1 file)

License police have already noticed the incompatible OpenSSL/SSLeay licenses in Sparkle’s License.txt after the recent pull. I've removed them again (and updated the README so we don't forget to do this next pull, including a reference to the discussion in bug 495620 and a hopefully-correct summary of the rationale). (We might want to consider at least filing this with Andy; he may not agree with the Mozilla legal interpretation, but if he does, it's one less thing for us to fork each update.)
Attachment #447559 - Flags: superreview?(stuart.morgan+bugzilla)
Comment on attachment 447559 [details] [diff] [review] Get license police off our backs (again) Oops, sorry :( sr=smorgan Can you make sure the README has a final newline before you land this?
Attachment #447559 - Flags: superreview?(stuart.morgan+bugzilla) → superreview+
CVS trunk and http://hg.mozilla.org/camino/rev/4d3dd289db01 (with the final newline and without a trailing EOL space in README).
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
(In reply to comment #0) > Created an attachment (id=447559) [details] > Get license police off our backs (again) ;-P Gerv
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: