jyapayne/nimble
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Allow locally stored package list files to be specified in config (#368)

Browse source
This commit is contained in:
Zach Smith 2017-06-25 12:52:01 -04:00
commit c89ca099a2
6 changed files with 153 additions and 62 deletions
Download patch file Download diff file Expand all files Collapse all files

9
readme.markdown
View file

@ -297,6 +297,10 @@ nimbleDir = r"C:\Nimble\"
[PackageList]
name = "CustomPackages"
url = "http://mydomain.org/packages.json"
[PackageList]
name = "Local project packages"
path = r"C:\Projects\Nim\packages.json"
```
You can currently configure the following in this file:
@ -307,12 +311,13 @@ You can currently configure the following in this file:
application packages. If ``true`` this will add ``chcp 65001`` to the
.cmd stubs generated in ``~/.nimble/bin/``.
**Default:** ``true``
* ``[PackageList]`` + ``name`` + ``url`` - You can use this section to specify
* ``[PackageList]`` + ``name`` + (``url``|``path``) - You can use this section to specify
a new custom package list. Multiple package lists can be specified. Nimble
defaults to the "Official" package list, you can override it by specifying
a ``[PackageList]`` section named "official". Multiple URLs can be specified
under each section, Nimble will try each in succession if
downloading from the first fails.
downloading from the first fails. Alternately, ``path`` can specify a
local file path to copy a package list .json file from.
* ``cloneUsingHttps`` - Whether to replace any ``git://`` inside URLs with
``https://``.
**Default: true**