On Mar 19, 2010, at 10:35 AM, Dimitri Glazkov wrote:
I agree that the idea of only pulling down expectations that you would actually need sounds great -- in fact we did try to think of ways of how this could be accomplished. So far, no great proposal materialized, but it doesn't mean the door of opportunity closes at this commit. I would think of this as more of a two-step solution: Step 1: Align Chromium port with the rest of the WebKit world and diminish the cost/pain of WebKit gardening. Step 2: Come up with a better way to track dependencies and optional components in WebKit. Step 3: Profit.
That sounds like a good order in which to approach things. I support aligning Chromium with other ports as the first step.
- Maciej _______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
