On Tue, Jul 12, 2011 at 9:01 PM, Adam Barth <[email protected]> wrote: > On Tue, Jul 12, 2011 at 8:34 PM, Ryosuke Niwa <[email protected]> wrote: >> On Tue, Jul 12, 2011 at 8:19 PM, Dirk Pranke <[email protected]> wrote: >>> >>> Hum. I take it back ... it still wouldn't be a tree, since >>> chromium-mac-leopard would fall back to chromium-mac-snowleopard, then >>> mac-leopard, but chromium-mac-snow-leopard would fall back to >>> mac-snowleopard (giving chromium-mac-snowleopard two parents). And it >>> looks like chromium-mac-leopard picks up 3,494 baselines from >>> mac-leopard :(. >> >> Can we create chromium-mac and move everything that's shared between >> chromium-mac-leopard and chromium-mac-snowleopard there? >> It seems wrong for chromium-mac-leopard to fallback to >> chromium-mac-snowleopard. > > This somewhat surprising fallback strategy is common across ports. > The "why" is explained on this wiki page: > > http://trac.webkit.org/wiki/LayoutTestsSearchPath >
In addition, we do actually have a 'chromium-mac'; we don't have a 'chromium-mac-snowleopard'. I think I mixed that in my mind while typing this with the apple mac ports, where there are mac-leopard, mac-sl, and mac ports (the latter representing lion/future). Once Lion ships, chromium will undoubtedly add a chromium-mac-snowleopard dir. -- Dirk _______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
