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.

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

[Improvement] Chocolatey package 'gitversion' should point to 'gitversion.portable' #2193

Closed
pauby opened this issue Mar 19, 2020 · 8 comments · Fixed by #3377
Closed

[Improvement] Chocolatey package 'gitversion' should point to 'gitversion.portable' #2193

pauby opened this issue Mar 19, 2020 · 8 comments · Fixed by #3377
Assignees
Milestone

Comments

@pauby
Copy link

pauby commented Mar 19, 2020

Is your improvement request related to a problem? Please describe.
It appears that the 'gittools' team maintain the Chocolatey package 'GitVersion' which is makred as 'Obsolete'. Given there is no other gitversion package, I would suggest it points to the 'gitversion.portable' package as it is causing confusion.

Detailed Description

Have the 'gitversion' Chocolatey package have 'gitversion.portable' as a dependency (and therefore act as a 'virtual package'.

Context

If you install the gitversion package you get an obsolete version that is simply a text file.

@arturcic
Copy link
Member

@gep13 what do you think about?

@gep13
Copy link
Member

gep13 commented Mar 19, 2020

@arturcic I was actually talking privately with @pauby about this...

What is the current state of the GitVersion package on NuGet? https://www.nuget.org/packages/gitversion

It doesn't look like it is currently being updated. Is it now deprecated?

I think the original reason that we stopped updating the GitVersion Package on Chocolatey was because we had a package named GitVersion being pushed to NuGet. If that is no longer the case, then creating a meta package on Chocolatey makes sense to me.

@arturcic
Copy link
Member

Agree, let's deprecate the GitVersion package and is there anything we should do in our build scripts to have the metapackage created?

@gep13
Copy link
Member

gep13 commented Mar 19, 2020

Yes, we will need to modify the build script to include the creation of that package. I can try and take a look at this at some point, but it won't be immediately.

@stale
Copy link

stale bot commented Jun 17, 2020

This issue has been automatically marked as stale because it has not had recent activity. After 30 days from now, it will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jun 17, 2020
@gep13 gep13 removed the stale label Jun 18, 2020
@ericnewton76
Copy link

2 years in the future... choco install GitVersion installs 1.0.0.1 lol

@gep13
Copy link
Member

gep13 commented Apr 14, 2022

@ericnewton76 that is a really helpful comment to leave on this issue! Thanks for sharing!

arturcic added a commit to arturcic/GitVersion that referenced this issue Feb 16, 2023
arturcic added a commit to arturcic/GitVersion that referenced this issue Feb 16, 2023
arturcic added a commit that referenced this issue Feb 17, 2023
#2193 - create a chocolatey metapackage
@arturcic arturcic added this to the 6.x milestone Feb 18, 2023
@arturcic arturcic modified the milestones: 6.x, 6.0.0-beta.1 Mar 2, 2023
@arturcic
Copy link
Member

arturcic commented Mar 2, 2023

🎉 This issue has been resolved in version 6.0.0-beta.1 🎉
The release is available on:

Your GitReleaseManager bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants