Add section about the Ruby script to the packaging page.

TBR=aa

Review URL: http://codereview.chromium.org/244025

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@27414 0039d316-1c4b-4281-b951-d872f2087c98

2 files changed, 43 insertions, 6 deletions

diff --git a/chrome/common/extensions/docs/packaging.html b/chrome/common/extensions/docs/packaging.html
index fe660f6..7793168 100755
--- a/chrome/common/extensions/docs/packaging.html
+++ b/chrome/common/extensions/docs/packaging.html
@@ -155,13 +155,20 @@
                   <a>h3Name</a>
                 </li>
               </ol>
-            </li><li jsinstance="*2">
+            </li><li jsinstance="2">
               <a href="#H2-2">Packaging at the command line</a>
               <ol>
                 <li jsinstance="*0" style="display: none; ">
                   <a>h3Name</a>
                 </li>
               </ol>
+            </li><li jsinstance="*3">
+              <a href="#ruby">Packaging on the Mac</a>
+              <ol>
+                <li jsinstance="*0" style="display: none; ">
+                  <a>h3Name</a>
+                </li>
+              </ol>
             </li>
             <div style="display: none; ">
               <li>
@@ -220,12 +227,12 @@ The private key is kept private
 and used to sign each version of the extension.
 </p>
 
-<!--
+<p class="comment">
 [PENDING: Perhaps mention that once the gallery is up,
 creating and updating a package will be much easier.
 Also refer to instructions on submitting an extension
 for inclusion in the gallery.]
--->
+</p>
 
 <a name="H2-0"></a><h2>Creating a package</h2>
 
@@ -343,7 +350,22 @@ For example:
 To suppress the dialog,
 add <code>--no-message-box</code> to the command.
 </p>
-</div>
+
+<h2 id="ruby">Packaging on the Mac</h2>
+
+<p>
+As of September 2009,
+Google Chrome for the Mac doesn't yet support creating packages.
+Until that support exists,
+you can use a Ruby script to create packages.
+See the following thread for details:
+</p>
+
+<blockquote>
+<a href="http://groups.google.com/group/chromium-extensions/browse_thread/thread/2e967e04d59fbacb">Chromium-extensions: extension packaging script</a>
+
+
+</blockquote></div>
 
         <!-- API PAGE -->
         <div class="apiPage" style="display: none; ">
diff --git a/chrome/common/extensions/docs/static/packaging.html b/chrome/common/extensions/docs/static/packaging.html
index 7592f05..997b982 100755
--- a/chrome/common/extensions/docs/static/packaging.html
+++ b/chrome/common/extensions/docs/static/packaging.html
@@ -11,12 +11,12 @@ The private key is kept private
 and used to sign each version of the extension.
 </p>
 
-<!--
+<p class="comment">
 [PENDING: Perhaps mention that once the gallery is up,
 creating and updating a package will be much easier.
 Also refer to instructions on submitting an extension
 for inclusion in the gallery.]
--->
+</p>
 
 <h2>Creating a package</h2>
 
@@ -137,3 +137,18 @@ chrome.exe --pack-extension=c:\myext --pack-extension-key=c:\myext.pem
 To suppress the dialog,
 add <code>--no-message-box</code> to the command.
 </p>
+
+<h2 id="ruby">Packaging on the Mac</h2>
+
+<p>
+As of September 2009,
+Google Chrome for the Mac doesn't yet support creating packages.
+Until that support exists,
+you can use a Ruby script to create packages.
+See the following thread for details:
+</p>
+
+<blockquote>
+<a href="http://groups.google.com/group/chromium-extensions/browse_thread/thread/2e967e04d59fbacb">Chromium-extensions: extension packaging script</a>
+
+