-
Notifications
You must be signed in to change notification settings - Fork 905
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extensions enhancements #588
Comments
Not a breaking change, but it may not clean up an older extension. |
Take it back, it's a breaking change if the users didn't create an extensions folder. |
Of course we could handle that scenario as well. |
ferventcoder
changed the title
Extensions should be added by only what is in the extensions folder and the name of the package
Extensions enhancements
Jan 27, 2016
ferventcoder
added a commit
to ferventcoder/choco
that referenced
this issue
Jan 27, 2016
Allow the package name to be either `*.extension` or `*.extensions`. Name the extensions folder by the name of the package id, minus `.extensions` and `.extension`. If the package has a folder extensions, only copy that folder, otherwise copy the enter package folder over to the extensions folder.
ferventcoder
added a commit
to ferventcoder/choco
that referenced
this issue
Jan 27, 2016
* stable: (chocolateyGH-588) Extensions enhancements
ferventcoder
added a commit
that referenced
this issue
May 6, 2016
Look for and be able to upgrade/uninstall extensions that were installed prior to 0.9.10 code, which removes the word ".extension" from the extension folder name and only copies in the extensions folder instead of the whole package.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
*.extension
or*.extensions
..extensions
and.extension
.This provides backwards compatibility with the older method if the user doesn't have a package that has an extensions folder.
The text was updated successfully, but these errors were encountered: