-
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
Add support for the --pin option on the install and upgrade commands #798
Comments
@CWempe I believe this has been discussed before and it's a pretty great idea! I'm surprised that there wasn't already an existing ticket (I searched), perhaps from the prior discussions one was not created. |
This adds a parameter to pin packages after install or upgrade. It re-uses the code in save_package_information to create the pin file.
Add specs for pin parameter for the install/upgrade commands
This adds a parameter to pin packages after install or upgrade. It re-uses the code in save_package_information to create the pin file.
Add specs for pin parameter for the install/upgrade commands
Any change in this area will require an upstream change in the chocolatey.extension to ensure that any and all new logic is respected there. |
This adds a parameter to pin packages after install or upgrade. It re-uses the code in save_package_information to create the pin file.
Add specs for pin parameter for the install/upgrade commands
This adds a parameter to pin packages after install or upgrade. It re-uses the code in save_package_information to create the pin file.
Add specs for pin parameter for the install/upgrade commands
This adds a parameter to pin packages after install or upgrade. It re-uses the code in save_package_information to create the pin file.
A follow up spike task has been created to confirm that this functionality continues to work as expected when the Chocolatey Licensed Extension is installed: https://gitlab.com/chocolatey/collaborators/choco-licensed/-/issues/631 |
Add tests that we are pinning packages when during upgrade and install when done with the `--pin` parameter.
Add tests that we are pinning packages when during upgrade and install when done with the `--pin` parameter.
Add tests that we are pinning packages when during upgrade and install when done with the `--pin` parameter.
Add tests that we are pinning packages when during upgrade and install when done with the `--pin` parameter.
Add tests that we are pinning packages when during upgrade and install when done with the `--pin` parameter.
This commit adds the `--pin` option to the list of available options in the table completion. The pin option was added to the install and upgrade command in this release.
This commit adds the `--pin` option to the list of available options in the table completion. The pin option was added to the install and upgrade command in this release.
* release/1.2.0: (374 commits) (maint) Add incoming arguments available in Licensed Extension (chocolatey#798) Add missing pin option in tab completion (chocolatey#2860) Add e2e tests for new PS cmdlet (maint) Fix Chocolatey path in docs generation (chocolatey#2860) Add new PS helper to get maintainer specific paths (chocolatey#2816) Update to latest Chocolatey NuGet.Core (chocolatey#2693) Re-add old resolve or load method (chocolatey#886) Update packages.config install logging (chocolatey#1185) Always pass in hook scripts event if empty Update tests/chocolatey-tests/commands/choco-outdated.Tests.ps1 (chocolatey#2801) Pin Chocolatey packages for outdated tests (chocolatey#886) Use specific strings for configurations (chocolatey#886) Add Pester tests for packages.config (chocolatey#886) Debug log Package configuration (chocolatey#1185) Be explicit with expected exit codes (maint) Pester test directory structure shuffle (chocolatey#1185) Add tests for hook scripts (maint) Minor formatting change (chocolatey#798) Add tests for pinning package on install (chocolatey#2787) Restore Chocolatey snapshot before sxs ...
🎉 This issue has been resolved in version 1.2.0 🎉 The release is available on: Your GitReleaseManager bot 📦🚀 |
* master: (maint) Add incoming arguments available in Licensed Extension (#798) Add missing pin option in tab completion (#2860) Add e2e tests for new PS cmdlet (maint) Fix Chocolatey path in docs generation (#2860) Add new PS helper to get maintainer specific paths (#2816) Update to latest Chocolatey NuGet.Core (#2693) Re-add old resolve or load method (#886) Update packages.config install logging
I just found out about chocolately and I think this is a great project!
Reading the issues here, I thought of a feature request.
I think it would be great if you could "pin" a package directly during (after) the installation.
Instead of
something like this
choco install googlechrome --pin
This would especialy come in handy when installing a list of packages via package.conf.
Then again this might be obsolet (in some cases) when #242 gets implemented.
The text was updated successfully, but these errors were encountered: