|
1 | 1 | # powerpkg
|
2 | 2 |
|
3 |
| - |
| 3 | + |
4 | 4 |
|
5 | 5 | `powerpkg` is a Windows-exclusive software deployment facilitator for enterprise environments, serving as an installation (or uninstallation) script for individual software packages; with optional actions, conditions and exceptions as core features. It is deliberately designed to use a [configuration file](#package-file-packagexml) model, ensuring a low learning curve, code standardization among every instance, and easy software updates (when available).
|
6 | 6 |
|
@@ -41,7 +41,7 @@ To begin testing powerpkg:
|
41 | 41 |
|
42 | 42 | **(2)**: Invoke `powerpkg.ps1`:
|
43 | 43 | ```shell
|
44 |
| -powershell.exe -NoProfile -ExecutionPolicy Unrestricted -File "example_package\powerpkg.ps1" |
| 44 | +powershell.exe -NoProfile -ExecutionPolicy Unrestricted -File "contrib\examplepackage\powerpkg.ps1" |
45 | 45 | ```
|
46 | 46 |
|
47 | 47 | **(3)**: *And that's it!*
|
@@ -210,7 +210,7 @@ Which, with a bit of customization, can become the following example:
|
210 | 210 | </Package>
|
211 | 211 | ```
|
212 | 212 |
|
213 |
| -To further familiarize yourself with powerpkg (and especially the above examples), continue reading the [Script Configuration](#script-configuration-configuration) and [Task Entry](#task-entry-taskentry) segments of this README. Examining the contents of the `\example_package` directory is also encouraged. |
| 213 | +To further familiarize yourself with powerpkg (and especially the above examples), continue reading the [Script Configuration](#script-configuration-configuration) and [Task Entry](#task-entry-taskentry) segments of this README. Examining the contents of the `\contrib\examplepackage` directory is also encouraged. |
214 | 214 |
|
215 | 215 | ### Script Configuration (`<Configuration>`)
|
216 | 216 |
|
@@ -508,7 +508,7 @@ To utilize the **`[Program]`** subparameter, you can verify the existence of a:
|
508 | 508 |
|
509 | 509 | - Open the `Programs and Features` applet of the Windows Control Panel, and retrieve the name of the installed program you wish to verify the existence of:
|
510 | 510 |
|
511 |
| -  |
| 511 | +  |
512 | 512 |
|
513 | 513 | - Within PowerShell, enter the following command:
|
514 | 514 |
|
@@ -546,7 +546,7 @@ To utilize the **`[Program]`** subparameter, you can verify the existence of a:
|
546 | 546 |
|
547 | 547 | - Open the `Programs and Features` applet of the Windows Control Panel, and retrieve the name of the installed program you wish to verify the existence of:
|
548 | 548 |
|
549 |
| -  |
| 549 | +  |
550 | 550 |
|
551 | 551 | - Then, specify a program name in this fashion:
|
552 | 552 |
|
|
0 commit comments