Mac-ify the app-based extensions folder name....

app/app_paths.cc

Index: app/app_paths.cc
===================================================================
--- app/app_paths.cc	(revision 20481)
+++ app/app_paths.cc	(working copy)
@@ -18,12 +18,16 @@
 
   FilePath cur;
   switch (key) {
+#if !defined(OS_MACOSX)

[Mark Mentovai, 2009/07/13 16:15:21]

Nobody will ever ask for DIR_THEMES on the Mac?

[Avi (use Gerrit), 2009/07/13 16:33:53]

They don't now, and if they start to, it'll be pretty obvious what the cause is.

+    // These are not "themes" that are user-created, but rather the dlls and
+    // pak files. On the Mac, we keep the pak files in the lproj folders.
     case app::DIR_THEMES:
       if (!PathService::Get(base::DIR_MODULE, &cur))
         return false;
       cur = cur.Append(FILE_PATH_LITERAL("themes"));
       create_dir = true;
       break;
+#endif
     case app::DIR_LOCALES:
       if (!PathService::Get(base::DIR_MODULE, &cur))
         return false;
@@ -40,8 +44,16 @@
     case app::DIR_EXTERNAL_EXTENSIONS:
       if (!PathService::Get(base::DIR_MODULE, &cur))
         return false;
+#if defined(OS_MACOSX)

[Mark Mentovai, 2009/07/13 16:15:21]

Do we support multiple extensions dirs?

[Avi (use Gerrit), 2009/07/13 16:33:53]

This is for extensions that ship with the app; this doesn't apply to extensions
that the users load.

+      // On Mac, built-in extensions are in Contents/Extensions, a sibling of
+      // the App dir. If there are none, it may not exist.
+      cur = cur.DirName();
+      cur = cur.Append(FILE_PATH_LITERAL("Extensions"));
+      create_dir = false;
+#else
       cur = cur.Append(FILE_PATH_LITERAL("extensions"));
       create_dir = true;
+#endif
       break;
     // The following are only valid in the development environment, and
     // will fail if executed from an installed executable (because the