posh-git
posh-git copied to clipboard
dahlbyk
The latest version is not available on chocolatey
The latest version of poshgit available on chocolatey is 0.7.3.1 Is it possible to update the chocolatey package to the latest version?
@dahlbyk Are you in the position to update the Chocolatey package?
I plan to, but don't want to release 1.0 to Chocolatey without addressing some of the issues reported for 0.x: https://github.com/dahlbyk/posh-git/labels/Chocolatey
Sooo... is 1.0.0 on Choco ever gonna happen?
It is, I've just had limited OSS time lately.
It will be really nice to get latest version on chocolatey. Just make things easier.
Is there a way to release it as a beta verion on Chocolatey? That way people who want it despite the remaining issues could still get it.
And still we wait... at this point @dahlbyk should remove the Choco install instructions from the README and delist the package from Choco, because it's causing more harm than good having an old version out there.
I've been hoping to "do it right" with the 1.0 release on Chocolatey (e.g. fix install location) and honestly just haven't wanted to spend time on it. For a year. 🤷♂️
Several people have tried to help, and I thank them. If someone seeing this is itching to make it happen, let's talk so I can get out of the way.
Lots more have complained, and I apologize. Glad to refund double what you paid.
I've been hoping to "do it right" with the 1.0 release on Chocolatey (e.g. fix install location) and honestly just haven't wanted to spend time on it. For a year. 🤷♂️
Several people have tried to help, and I thank them. If someone seeing this is itching to make it happen, let's talk so I can get out of the way.
Lots more have complained, and I apologize. Glad to refund double what you paid.
Fair, and I apologise for my rudeness. I'm just frustrated because this is such a great project and not having the latest and greatest version on choco is IMO harming the project's profile.
Hi,
I am a maintainer of multiple Chocolatey packages and user of posh-git
I am happy to take over, if you want
Verstuurd vanaf mijn iPhone
On 23 Feb 2022, at 15:42, Keith Dahlby @.***> wrote:
I've been hoping to "do it right" with the 1.0 release on Chocolatey (e.g. fix install location) and honestly just haven't wanted to spend time on it. For a year. 🤷♂️
Several people have tried to help, and I thank them. If someone seeing this is itching to make it happen, let's talk so I can get out of the way.
Lots more have complained, and I apologize. Glad to refund double what you paid.
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.
Out of curiosity, what is wrong with using PowerShell's built-in module manager to install this module e.g. install-module posh-git -force?
Out of curiosity, what is wrong with using PowerShell's built-in module manager to install this module e.g.
install-module posh-git -force?
The Chocolatey module depends on Git, so it's a one-line install to get both. It does seem less relevant now that PowerShellGet is installed by default.
Of course, I'm also slacking on getting posh-git set up to be an install option with Git for Windows, which means it ends up also being a parameter on that package. So perhaps the ultimate correct answer might just be deprecating the standalone package and changing install instructions to something like:
choco install git.install --params "/PoshGit"
Or we could make the argument that the Chocolatey package should just include posh-git by default, with a /NoPoshGit option. Chocolatey users typically being command line users, after all.
@IanKemp I was grumpy earlier, but this conversation wouldn't have moved forward without the nudge. Thank you.
So perhaps the ultimate correct answer might just be deprecating the standalone package…
You're all welcome to weight in: https://github.com/chocolatey-community/chocolatey-packages/discussions/1809
@mkevenaar I am a maintainer of multiple Chocolatey packages and user of posh-git
I am happy to take over, if you want
I appreciate the offer. I ultimately want to automate release to the PowerShell Gallery and Chocolatey (if we end up maintaining that package), if you or anyone have experience with that.
@pauby has also tried to help with the Chocolatey situation in the past, and likely has additional thoughts since then.
I responded over at the issue you mentioned above. There has been a lot of talk about this package in the past for many reasons (I don't want to drag them up).
Personally speaking (ie. not from my position at Chocolatey) I think you need to:
- Pass the package over to somebody who can maintain it in a standard consistent way (@mkevenaar has offered and I've offered in the past (I maintain a number of PowerShell modules in the Chocolatey Community Repository such as dbatools) but the chocolatey-community repository may be best);
- Have somebody create the Chocolatey package for you in a standard consistent way and you update it with the release going forward with the changes (ie. version change, checksum / bundled module)
I say this only from a place of understanding of the place you are in @dahlbyk (I've been there), the place the package is in and what I feel (that's important, this is just my opinion)) best for the community and you. There is no finality of handing the package off. You can always come back to it later when you have the time, energy or desire to pick it back up again. If that is the way you are thinking then the people / place I mention in 1. above will happily pass it back to you.
