extern/boxes
1
0
Fork 0
mirror of https://github.com/ascii-boxes/boxes.git synced 2025-01-07 06:28:57 +01:00
Code Issues Packages Projects Releases Wiki Activity

Fix path references in description text of choco package

Browse Source
This commit is contained in:
Thomas Jensen 2019-04-05 15:46:48 +02:00
parent 859b94be2a
commit b6a2f5d82f
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
boxes.portable.nuspec
View File

@ -12,7 +12,7 @@ and repair those boxes, too. You can easily make your own box designs if you wis
already provided. already provided.
*Boxes* is a portable application (hence the `.portable` suffix in the choco package ID). It is installed into *Boxes* is a portable application (hence the `.portable` suffix in the choco package ID). It is installed into
the package directory `%ChocolateyInstall%\lib\boxes`. Chocolatey makes *boxes* available to you on the `PATH` the package directory `%ChocolateyInstall%\lib\boxes.portable`. Chocolatey makes *boxes* available to you on the `PATH`
via its `%ChocolateyInstall%\bin` directory. This is the only official *boxes* choco package. via its `%ChocolateyInstall%\bin` directory. This is the only official *boxes* choco package.
### Examples ### Examples
@ -69,8 +69,8 @@ A more complex call might look like this:
At some point, you may wish to modify existing box designs or even add your own. At some point, you may wish to modify existing box designs or even add your own.
When that happens, you may find that you don't have the necessary access permissions to modify boxes.cfg in When that happens, you may find that you don't have the necessary access permissions to modify boxes.cfg in
`%ChocolateyInstall%\lib\boxes` directly. In that case, make a copy of boxes.cfg and place it in one of the `%ChocolateyInstall%\lib\boxes.portable\tools` directly. In that case, make a copy of boxes.cfg and place it in one of
precedent locations, where *boxes* finds it before the original. When reading the config file, *boxes* will try the precedent locations, where *boxes* finds it before the original. When reading the config file, *boxes* will try
these locations (in order): these locations (in order):
1. The file specified by the environment variable `BOXES`. 1. The file specified by the environment variable `BOXES`.