[Webkit-unassigned] [Bug 77200] [npapi] Master bug to synchronize with npapi-sdk

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=77200


Stuart Morgan <stuartmorgan at chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |stuartmorgan at chromium.org




--- Comment #2 from Stuart Morgan <stuartmorgan at chromium.org>  2012-01-27 04:35:29 PST ---
> And it is difficult to use is for plugin development.

Why would you use it for plugin development? The whole point of the npapi-sdk project is that plugin developers can (and should) use those headers instead of using one random browser's headers.

> Existing bug https://bugs.webkit.org/show_bug.cgi?id=38666 is resolved as fixed, but it is not.

FWIW, I closed that bug because I got from "wildly different" (to the point that diffing the files was essentially meaningless) to "specific points of divergence", after which point having a meta-bug was not particularly useful.

> And I wouldn't close this bug until headers from http://code.google.com/p/npapi-sdk/ are taken
> from its trunk (maybe with help of svn externals).

That makes this bug uncloseable. Source-compatibility is not a requirement for the npapi-sdk project, which means that if a project always pulls trunk then it is subject to breakage at any moment for reasons beyond its control. It also makes building a specific older revision of the project as it existed at that time impossible. Doing that in WebKit would be a *terrible* idea. The best-case scenario for browser vendors would be to pull specific revisions, using something like Chromium's DEPS system.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.