Correction:
I've made some further server-side changes so as to avoid any
warnings from CVS on the client side.
update-webkit should work _without_errors_or_warnings_ for all users,
including those with an existing SVGSupport directory.
-eric
On Sep 1, 2005, at 2:53 AM, Eric Seidel wrote:
You can ignore this if you do not have a checked out copy of
SVGSupport.
Tonight we finally landed several important changes, two of which
affect all users:
1. As previously warned, the tabs -> spaces change went in
(4752). Anyone who has modifications to their local SVGSupport
directory _which_include_tabs_, should convert their modifications
from tabs -> spaces before updating from CVS, or risk lots of
conflicts!
2. The ./impl/* -> ./* file move finally went in (4790). This was
a *server side* move, and thus may confuse your CVS client. If you
do not have any local modifications to SVGSupport, it's cleanest to
just remove all SVG support and start-over:
rm WebCore/kdom
rm WebCore/kcanvas
rm WebCore/ksvg2
rm WebCore/WebCore+SVG
rm -r SVGSupport
WebKitTools/checkout-svg
If you do have local modifications to SVGSupport, you can go ahead
and use the normal update-webkit, but you will see several
(harmless) warnings logged to stderr.
Thats all. Happy SVG hacking!
-eric
_______________________________________________
webkit-dev mailing list
[email protected]
http://www.opendarwin.org/mailman/listinfo/webkit-dev
_______________________________________________
webkit-dev mailing list
[email protected]
http://www.opendarwin.org/mailman/listinfo/webkit-dev
