Permalink
Browse files

clarifying variable resolution

hat-tip to @mikereinstein
  • Loading branch information...
1 parent 356df23 commit aa00a77796279125e560575d712ba062f14e80e6 @alunny committed Sep 12, 2012
Showing with 11 additions and 4 deletions.
  1. +11 −4 README.md
View
@@ -310,10 +310,16 @@ series of capital letters, digits and underscores. For the above example, the
android:name="$PACKAGE_NAME.permission.C2D_MESSAGE"/>
Tools using this specification should replace variable references with the
-correct value, if specified, or the empty string otherwise. The value of the
-variable reference may be detected (in this case, from the `AndroidManifest.xml`
-file, or specified by the user of the tool; the exact process is dependent on
-the particular tool.
+correct value, if specified, or the empty string otherwise.
+
+The value of the variable reference may be detected by the plugin installation
+tool (in this case, by reading the `AndroidManifest.xml` file), or specified
+by the end-user. One approach could be using environment variables:
+
+ $ pluginstall android . ~/my-plugin PACKAGE_NAME=com.foo
+
+Variable resolution could also be specified programmatically, depending how the
+plugin installer is called.
Certain variable names should be reserved - these are listed below.
@@ -331,6 +337,7 @@ Fil Maj
## Contributors
Michael Brooks
+Mike Reinstein
## License

0 comments on commit aa00a77

Please sign in to comment.