On 12/27/06, Axel Dörfler <axeld@xxxxxxxxxxxxxxxx> wrote:
If that should be a permanent storage, we already have vendor branches to put the verbatim packages under. If WebKit is done, I would guess we'd be very interested to make it part of Haiku, anyway, so a 3rdparty / wouldn't be used for that either.
Well I can't predict the future of course, but I think the best bet for a future Haiku/WebKit relationship would be to keep a separate WebKit (it is quite a lot of source, almost as much as Haiku I suspect) which would be (hopefully) easy to download and build to produce libWebKit.so. Then on the Haiku side we would have maybe BHTMLView which uses libWebKit.so and then our browser source which again would use libWebKit.so. From what I've seen the WebKit community seems friendly towards porting and making WebKit more portable in its core, so it is conceivable that after the needed work we could just download the WebKit source from their repository and quickly build a Haiku/BeOS version. This way we can be sure to make use of improvements to the Mac and Linux versions of WebKit without complicated merging and patching of a separate branch in our source tree. Regards, Ryan