Changes

no edit summary
Line 9: Line 9:  
=== Self-contained binary bundles ===
 
=== Self-contained binary bundles ===
   −
This mode is intended for special cases when a sweet needs to be used without Zero Install and Sweets, containing all dependencies bundled. For binary based sweets, resulting bundle will contain binaries built only for the environment that is being used to create this bundle. Thus, make sure that bundle will be used in exactly the same environment as original one.
+
This mode is intended for special cases, when a sweet needs to be used without Zero Install and Sweets. In this mode all dependencies are bundled. For binary based sweets, the resulting bundle will contain binaries built only for the environment that is being used to create this bundle. Thus, make sure that the new bundle will be used in exactly the same environment as the original one.
   −
To build self-contained binary bundle, use {{Code|bindist}} command:
+
To build a self-contained binary bundle, use the {{Code|bindist}} command:
    
  sweet bindist <SWEET>
 
  sweet bindist <SWEET>
   −
The resulting bundle will be placed to the current directory.
+
The resulting bundle will be placed into the current directory.
    
After extracting, it might be used in several ways:
 
After extracting, it might be used in several ways:
   −
* for libraries, source the shell file in {{Code|<SWEET-NAME>/binding}} directory;
+
* for libraries, source the shell file in the {{Code|<SWEET-NAME>/binding}} directory;
 
* for applications, execute the script {{Code|<SWEET-NAME>/<APPLICATION>}}, the default application name is {{Code|run}}.
 
* for applications, execute the script {{Code|<SWEET-NAME>/<APPLICATION>}}, the default application name is {{Code|run}}.