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

Status: RESOLVED FIXED

Description

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

Created attachment 447559 [details] [diff] [review]
Get license police off our backs (again)

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.)

Comment 1

[Stuart Morgan]

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?

Comment 2

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

CVS trunk and http://hg.mozilla.org/camino/rev/4d3dd289db01 (with the final newline and without a trailing EOL space in README).

Comment 3

[Gervase Markham [:gerv] (not reading bugmail)]

(In reply to comment #0)
> Created an attachment (id=447559) [details]
> Get license police off our backs (again)

;-P

Gerv