Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Move Chocolatey package into this repo #449

Open
pascalberger opened this issue Nov 16, 2020 · 2 comments
Open

Move Chocolatey package into this repo #449

pascalberger opened this issue Nov 16, 2020 · 2 comments
Assignees
@pascalberger
Labels
Improvement

Comments

@pascalberger
Copy link
Member

There's a Chocolatey package (https://chocolatey.org/packages/vscode-cake) for this extension which is currently maintained outside. We should move it into this repo and publish as part of the build process.

Since package is released with a 1.0.0.x version this could not be done before 1.0 is released. Once code is moved Chocolatey package should be changed to include VSIX into the package and install specific version (through Chocolatey VSCode extension)
@pascalberger pascalberger mentioned this issue Nov 16, 2020
Open
@gep13 gep13 added this to the 1.0.1 milestone Nov 16, 2020
gep13 added a commit that referenced this issue Nov 16, 2020
@gep13
(GH-449) Remove Chocolatey package
3cd2712 
Currently, we can't ship a new Chocolatey package from this extension,
since there is already a > 1.0.0 package version out there. Once we
ship 1.0.0 of the extension, we can then look to bring this back in.
@ymartin59
Copy link

ymartin59 commented Jan 28, 2021 •
edited
Loading

OK but if we install vscode-cake from Chocolatey... it may be interesting that it works out-of-the-box with Chocolatey "cake" and "cake-bakery" packages... but it is not yet true because of Shim cake-build/bakery#115

@gep13
Copy link
Member

gep13 commented Dec 6, 2021

Going to bump this one from the 2.0.0 milestone, as there are some questions here that need to be addressed.

@gep13 gep13 removed this from the 2.0.0 milestone Dec 6, 2021
@gep13 gep13 mentioned this issue Dec 6, 2021
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pascalberger pascalberger

Labels
Improvement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@gep13 @pascalberger @ymartin59