Skip to content

Commit 0d3121a

Browse files
committed
readme: change dir names and paths
1 parent bc2ee46 commit 0d3121a

File tree

7 files changed

+5
-6
lines changed

7 files changed

+5
-6
lines changed

README.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# powerpkg
22

3-
![](/readme/header.gif)
3+
![](/img/header.gif)
44

55
`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).
66

@@ -41,7 +41,7 @@ To begin testing powerpkg:
4141

4242
**(2)**: Invoke `powerpkg.ps1`:
4343
```shell
44-
powershell.exe -NoProfile -ExecutionPolicy Unrestricted -File "example_package\powerpkg.ps1"
44+
powershell.exe -NoProfile -ExecutionPolicy Unrestricted -File "contrib\examplepackage\powerpkg.ps1"
4545
```
4646

4747
**(3)**: *And that's it!*
@@ -210,7 +210,7 @@ Which, with a bit of customization, can become the following example:
210210
</Package>
211211
```
212212

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.
214214

215215
### Script Configuration (`<Configuration>`)
216216

@@ -508,7 +508,7 @@ To utilize the **`[Program]`** subparameter, you can verify the existence of a:
508508
509509
- 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:
510510
511-
![Programs and Features](/readme/example_verifyinstall_program.gif)
511+
![Programs and Features](/img/example_verifyinstall_program.gif)
512512
513513
- Within PowerShell, enter the following command:
514514
@@ -546,7 +546,7 @@ To utilize the **`[Program]`** subparameter, you can verify the existence of a:
546546
547547
- 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:
548548
549-
![Programs and Features](/readme/example_verifyinstall_program.gif)
549+
![Programs and Features](/img/example_verifyinstall_program.gif)
550550
551551
- Then, specify a program name in this fashion:
552552

badge/project_status.svg

Lines changed: 0 additions & 1 deletion
This file was deleted.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.

0 commit comments

Comments
 (0)