-
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
Deprecate side-by-side installs #2787
Comments
This commit makes the necessary changes to deprecate side by side installations in the Chocolatey CLI codebase as well as warn the users about any installations for side-by-side. Including if the user have side-by-side installations already installed on their system.
This commit makes the necessary changes to deprecate side by side installations in the Chocolatey CLI codebase as well as warn the users about any installations for side-by-side. Including if the user have side-by-side installations already installed on their system.
This commit makes the necessary changes to deprecate side by side installations in the Chocolatey CLI codebase as well as warn the users about any installations for side-by-side. Including if the user have side-by-side installations already installed on their system.
…de-installs (#2787) Deprecate side by side installations
The info tests enable a proxy that prevents the side by side tests from actually working correctly. This restores the Snapshot so we have a fresh Chocolatey installation to test against.
The Licensed Extension extends the Info command. Our current tests expect it to output a deprecation message. We will want to assess if we duplicate that message into the Licensed Extension, or update the test to be FOSSOnly. Added the Upstream Change label for tracking, and will discuss more at planning meeting. |
The info tests enable a proxy that prevents the side by side tests from actually working correctly. This restores the Snapshot so we have a fresh Chocolatey installation to test against.
The info tests enable a proxy that prevents the side by side tests from actually working correctly. This restores the Snapshot so we have a fresh Chocolatey installation to test against.
The info tests enable a proxy that prevents the side by side tests from actually working correctly. This restores the Snapshot so we have a fresh Chocolatey installation to test against.
The info tests enable a proxy that prevents the side by side tests from actually working correctly. This restores the Snapshot so we have a fresh Chocolatey installation to test against.
This is being reopened as we need to pickup this task:
What was needed here was documentation that explained the alternative to side-by-side installs and specifically why it needs done. This was envisaged being a page in the docs. |
* 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 ...
@pauby I have created an issue on the docs repository to track the progress of this here: chocolatey/docs#581 |
🎉 This issue has been resolved in version 1.2.0 🎉 The release is available on: Your GitReleaseManager bot 📦🚀 |
I miss any info about why this feature needs to be removed beside planned to be deprecated, which from our company's perspective is a very unfortunate decision. |
@thoscut The reason this is being removed is that it never worked the way it was intended to, caused us no end of support issues for a very small number of customers who used it. The intention was to create the document before the release so it was available. That was unfortunately missed and is on me. |
I don't see any docs for fixing that notice
How can i resolve this? |
@viceice This issue is closed. Can you raise a separate issue for this? I'm assuming you didn't install those KB packages as side-by-side installs. I'm going to lock this issue now to prevent comments that would be missed by the team. |
Is Your Feature Request Related To A Problem? Please describe.
Side-by-side installs are planned to be deprecated in a future (potentially version 2.0) of Chocolatey CLI. We need to ensure we properly deprecate this in the collection.
Note that before this is deprecated, we will have documentation describing the options available to continue to have similar functionality.
Describe The Solution. Why is it needed?
Side-by-side installs are being deprecated.
Additional Context.
Before this is deprecated, we will have documentation describing the options available to continue to have similar functionality.
Related Issues
None.
The text was updated successfully, but these errors were encountered: