-
-
Notifications
You must be signed in to change notification settings - Fork 726
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
Add OutputDirectory property for Chocolatey Aliases #1146
Comments
@pascalberger yes and no. That commit is really tricking chocolatey into thinking that it is running in the specified output directory, hence, that is where the output file goes. Now in the chocolatey client there is an option to specify the output directory. The chocolatey aliases within Cake should correctly use that setting. |
i.e. within the ChocolateyPackRunner, set the |
@gep13 Ah, missed this :) I can create a PR for this. Can we expect users to have Chocolatey >= 0.10.0 installed? |
@pascalberger that is a difficult one. The stance I personally take on this is that the aliases should work against the current latest version of the underlying tool, however, we should probably do a check in this instance to make sure that the version is high enough before attempting to run that command. Or, I wonder, would an earlier version of chocolatey just ignore it? Perhaps worth a quick investigation. |
Any news on this? |
- Make use of full option name - Make sure to always use = in option value - Add common options to all commands - Add new options that have been added since aliases first created
- Make use of full option name - Make sure to always use = in option value - Add common options to all commands - Add new options that have been added since aliases first created
🎉 This issue has been resolved in version v3.0.0 🎉 The release is available on: Your GitReleaseManager bot 📦🚀 |
Once 0.10.0 is released:
chocolatey/choco#598 (comment)
The text was updated successfully, but these errors were encountered: