c327476da9
* Upgrade msys2 packages The old ones pull in dependencies that have disappeared. changelog_begin changelog_end * No special assignment changelog_begin changelog_end |
||
|---|---|---|
| .. | ||
| 7zip.json | ||
| bazel.json | ||
| cacert.json | ||
| curl-7.73.0.json | ||
| java-openjdk-8u201.json | ||
| maven-3.6.1.json | ||
| msys2.json | ||
| nodejs-12.17.0.json | ||
| nsis-3.04.json | ||
| python-3.8.2.json | ||
| README.md | ||
| stack.json | ||
| toxiproxy.json | ||
| vcredist.json | ||
Tools manifests files
DADEW uses Scoop for tools provisioning. Tools manifest files are in fact Scoop's App manifest files and are documented here.
Tool name mentioned in .dadew file is the name of the manifest file (excluding it's .json extention).
Adding new tool
To add new tool:
- create new manifest file under
/dev-env/windows/manifests/folder, ensuring:- it follows the naming convention of
<name>-<version>.json - it sources binaries from a URL, which points to specific version of the tool and is unlikely to change
- it follows the naming convention of
- add a
<name>-<version>entry to/.dadewfile, extendingtoolselement list
Adding new version of the existing tool
Process of adding new version of the existing tool is very similar to adding new one, but:
- you should not modify existing manifest files to allow backward compatibility of win-dev-env,
- you should not remove the old tool's manifest file
- you should replace the existing entry in the
/.dadewfile with the new one
Updating the existing version of a tool
In some cases there is a need to update the existing manifest file, for example to introduce an environment variable or
update the binary minor release version. In such case manifest file can be changed in-place. dadew will detect such change
and perform the tool re-installation on dadew sync call automatically.
Source of manifests
Default set of Scoop App manifests (also called a default bucket) can be found here.
Other buckets are listed in Scoop's buckets.json file.