kevin/asdf
1
Fork 0
mirror of https://github.com/asdf-vm/asdf.git synced 2024-11-15 01:28:17 -07:00
Code Issues Packages Projects Releases Wiki Activity

asdf is now qwer

Browse Source
This commit is contained in:
Akash Manohar J 2015-07-28 13:49:09 +05:30
parent 88966ac262
commit c11e9f69a3
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/creating-plugins.md
View File

@ -38,9 +38,9 @@ List executables for the specified version of the tool. Must print a string with
bin tools veggies
```
This will instruct asdf to create shims for the files in `<install-path>/bin`, `<install-path>/tools` and `<install-path>/veggies`
This will instruct qwer to create shims for the files in `<install-path>/bin`, `<install-path>/tools` and `<install-path>/veggies`
If this script is not specified, asdf will look for the `bin` dir in an installation and create shims for those.
If this script is not specified, QWER will look for the `bin` dir in an installation and create shims for those.
#### bin/exec-env
@ -54,6 +54,6 @@ Uninstalls a specific version of a tool.
**PLEASE use this feature only if absolutely required**
asdf allows custom shim templates. For an executable called `foo`, if there's a `shims/foo` file in the plugin, then asdf will copy that file instead of using it's standard shim template.
qwer allows custom shim templates. For an executable called `foo`, if there's a `shims/foo` file in the plugin, then qwer will copy that file instead of using it's standard shim template.
This must be used wisely. For now AFAIK, it's only being used in the Elixir plugin, because an executable is also read as an Elixir file apart from just being an executable. Which makes it not possible to use the standard bash shim.