diff options
| author | kathyw@google.com <kathyw@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-10-01 03:59:00 +0000 |
|---|---|---|
| committer | kathyw@google.com <kathyw@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-10-01 03:59:00 +0000 |
| commit | 8bc7810ae3c5b608a9668c765bf83c30a6461aa0 (patch) | |
| tree | 72f13ffde49f1e049fa2fd73350db340305e8a2a /chrome | |
| parent | fcc23e84efb0aa42e00f79d5fa1798b5604d7a28 (diff) | |
| download | chromium_src-8bc7810ae3c5b608a9668c765bf83c30a6461aa0.zip chromium_src-8bc7810ae3c5b608a9668c765bf83c30a6461aa0.tar.gz chromium_src-8bc7810ae3c5b608a9668c765bf83c30a6461aa0.tar.bz2 | |
Minor copyedits to packaging to provide better context.
TBR=aa
Review URL: http://codereview.chromium.org/255033
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@27701 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome')
| -rwxr-xr-x | chrome/common/extensions/docs/packaging.html | 17 | ||||
| -rwxr-xr-x | chrome/common/extensions/docs/static/packaging.html | 17 |
2 files changed, 22 insertions, 12 deletions
diff --git a/chrome/common/extensions/docs/packaging.html b/chrome/common/extensions/docs/packaging.html index 7793168..2055aea 100755 --- a/chrome/common/extensions/docs/packaging.html +++ b/chrome/common/extensions/docs/packaging.html @@ -218,11 +218,17 @@ <div id="pageData-showTOC" class="pageData">true</div> <p> -Extensions are packaged as signed zip files -with the file extension "crx" -(for example, <code>myextension.crx</code>). -Each extension has its own unique key pair. -The public key is used as the unique identifier for the extension. +This page describes how to package your extension. +As the <a href="overview.html">Overview</a> explains, +extensions are packaged as signed ZIP files +with the file extension "crx" — +for example, <code>myextension.crx</code>. +</p> + +<p> +When you package an extension, +the extension is assigned a unique key pair. +The public key is used as the identifier for the extension. The private key is kept private and used to sign each version of the extension. </p> @@ -354,7 +360,6 @@ add <code>--no-message-box</code> to the command. <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. diff --git a/chrome/common/extensions/docs/static/packaging.html b/chrome/common/extensions/docs/static/packaging.html index 997b982..42f5ab3 100755 --- a/chrome/common/extensions/docs/static/packaging.html +++ b/chrome/common/extensions/docs/static/packaging.html @@ -2,11 +2,17 @@ <div id="pageData-showTOC" class="pageData">true</div> <p> -Extensions are packaged as signed zip files -with the file extension "crx" -(for example, <code>myextension.crx</code>). -Each extension has its own unique key pair. -The public key is used as the unique identifier for the extension. +This page describes how to package your extension. +As the <a href="overview.html">Overview</a> explains, +extensions are packaged as signed ZIP files +with the file extension "crx" — +for example, <code>myextension.crx</code>. +</p> + +<p> +When you package an extension, +the extension is assigned a unique key pair. +The public key is used as the identifier for the extension. The private key is kept private and used to sign each version of the extension. </p> @@ -141,7 +147,6 @@ add <code>--no-message-box</code> to the command. <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. |